From: Mike Rapoport <rppt@kernel.org>
To: Ankit Khushwaha <ankitkhushwaha.linux@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Shuah Khan <shuah@kernel.org>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] selftests/mm/uffd: initialize char variable to Null
Date: Thu, 27 Nov 2025 07:06:21 +0200 [thread overview]
Message-ID: <aSfcTS3xf64zLdbR@kernel.org> (raw)
In-Reply-To: <20251126160830.52124-1-ankitkhushwaha.linux@gmail.com>
On Wed, Nov 26, 2025 at 09:38:30PM +0530, Ankit Khushwaha wrote:
> In "uffd-stress.c" & "uffd-unit-tests.c". address of char variable having
> garbage value (uninitialized) is passed to 'write' syscall triggers
> warning.
>
> uffd-stress.c:246:39: warning: variable 'c' is uninitialized when
> passed as a const pointer argument here
> [-Wuninitialized-const-pointer]
>
> uffd-unit-tests.c:581:31: warning: variable 'c' is uninitialized
> when passed as a const pointer argument here
> [-Wuninitialized-const-pointer]
>
> so the fix is to assign char variable to '\0' to prevent writing of
> garbage value.
>
> Signed-off-by: Ankit Khushwaha <ankitkhushwaha.linux@gmail.com>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> this warning is raised with clang version 21.1.5 (Fedora 21.1.5-1.fc43).
> ---
> tools/testing/selftests/mm/uffd-stress.c | 2 +-
> tools/testing/selftests/mm/uffd-unit-tests.c | 8 ++++----
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/uffd-stress.c b/tools/testing/selftests/mm/uffd-stress.c
> index b51c89e1cd1a..700fbaa18d44 100644
> --- a/tools/testing/selftests/mm/uffd-stress.c
> +++ b/tools/testing/selftests/mm/uffd-stress.c
> @@ -241,7 +241,7 @@ static int stress(struct uffd_args *args)
> return 1;
>
> for (cpu = 0; cpu < gopts->nr_parallel; cpu++) {
> - char c;
> + char c = '\0';
> if (bounces & BOUNCE_POLL) {
> if (write(gopts->pipefd[cpu*2+1], &c, 1) != 1)
> err("pipefd write error");
> diff --git a/tools/testing/selftests/mm/uffd-unit-tests.c b/tools/testing/selftests/mm/uffd-unit-tests.c
> index f917b4c4c943..f4807242c5b2 100644
> --- a/tools/testing/selftests/mm/uffd-unit-tests.c
> +++ b/tools/testing/selftests/mm/uffd-unit-tests.c
> @@ -543,7 +543,7 @@ static void uffd_minor_test_common(uffd_global_test_opts_t *gopts, bool test_col
> {
> unsigned long p;
> pthread_t uffd_mon;
> - char c;
> + char c = '\0';
> struct uffd_args args = { 0 };
> args.gopts = gopts;
>
> @@ -759,7 +759,7 @@ static void uffd_sigbus_test_common(uffd_global_test_opts_t *gopts, bool wp)
> pthread_t uffd_mon;
> pid_t pid;
> int err;
> - char c;
> + char c = '\0';
> struct uffd_args args = { 0 };
> args.gopts = gopts;
>
> @@ -819,7 +819,7 @@ static void uffd_events_test_common(uffd_global_test_opts_t *gopts, bool wp)
> pthread_t uffd_mon;
> pid_t pid;
> int err;
> - char c;
> + char c = '\0';
> struct uffd_args args = { 0 };
> args.gopts = gopts;
>
> @@ -1125,7 +1125,7 @@ uffd_move_test_common(uffd_global_test_opts_t *gopts,
> {
> unsigned long nr;
> pthread_t uffd_mon;
> - char c;
> + char c = '\0';
> unsigned long long count;
> struct uffd_args args = { 0 };
> char *orig_area_src = NULL, *orig_area_dst = NULL;
> --
> 2.52.0
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2025-11-27 5:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 16:08 Ankit Khushwaha
2025-11-27 5:06 ` Mike Rapoport [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aSfcTS3xf64zLdbR@kernel.org \
--to=rppt@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ankitkhushwaha.linux@gmail.com \
--cc=david@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=peterx@redhat.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox