Re: [PATCH] setup: avoid uninitialized use of is_safe in ensure_valid_ownership

[Carlo Arenas <carenas@gmail.com>]

On Wed, Apr 27, 2022 at 1:33 AM Matheus Valadares <me@m28.io> wrote:
>
> C99 standard §6.7.8 (Initialization)/21,
>
> If there are fewer initializers in a brace-enclosed list than there are elements or members of an aggregate, or fewer characters in a string literal used to initialize an array of known size than there are elements in the array, the remainder of the aggregate shall be initialized implicitly the same as objects that have static storage duration.

Thanks, I will include the change to remove the path initializer and
add instead the is_safe one as part of my bigger change, but FWIW the
following doesn't even trigger a warning with the highest level we
have with neither a recent clang or gcc or even the cppcheck static
analyzer, but leave and uses is_safe uninitialized.

diff --git a/setup.c b/setup.c
index 17c7f5fc1dc..28d008145fa 100644
--- a/setup.c
+++ b/setup.c
@@ -1122,7 +1122,9 @@ static int safe_directory_cb(const char *key,
const char *value, void *d)

 static int ensure_valid_ownership(const char *path)
 {
-       struct safe_directory_data data = { .path = path, .is_safe = 0 };
+       struct safe_directory_data data;
+
+       data.path = path;

        if (!git_env_bool("GIT_TEST_ASSUME_DIFFERENT_OWNER", 0) &&
            is_path_owned_by_current_user(path))

Carlo