mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: <ntfs3@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	<llvm@lists.linux.dev>, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] ntfs3: Restore NULL folio initialization in ntfs_writepages()
Date: Fri, 16 Jan 2026 14:46:06 +0100	[thread overview]
Message-ID: <104e68d7-9b50-4318-ae64-8a22093c6e92@paragon-software.com> (raw)
In-Reply-To: <20260105-ntfs3-restore-null-folio-init-v1-1-432093703dfd@kernel.org>

On 1/5/26 20:17, Nathan Chancellor wrote:

> Clang warns (or errors with CONFIG_WERROR=y):
>
>    fs/ntfs3/inode.c:1021:6: error: variable 'folio' is used uninitialized whenever 'if' condition is true [-Werror,-Wsometimes-uninitialized]
>     1021 |         if (is_resident(ni)) {
>          |             ^~~~~~~~~~~~~~~
>    fs/ntfs3/inode.c:1024:48: note: uninitialized use occurs here
>     1024 |                 while ((folio = writeback_iter(mapping, wbc, folio, &err)))
>          |                                                              ^~~~~
>
> folio should be initialized to NULL for the first iteration of
> writeback_iter() to start the loop properly. Restore the NULL
> initialization of folio that was lost in the recent iomap conversion to
> clear up the warning.
>
> Fixes: 099ef9ab9203 ("fs/ntfs3: implement iomap-based file operations")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202601010644.FIhOXy6Y-lkp@intel.com/
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> ---
>   fs/ntfs3/inode.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ntfs3/inode.c b/fs/ntfs3/inode.c
> index b969ad7c3258..438d468f28ba 100644
> --- a/fs/ntfs3/inode.c
> +++ b/fs/ntfs3/inode.c
> @@ -1019,7 +1019,7 @@ static int ntfs_writepages(struct address_space *mapping,
>   		return -EIO;
>   
>   	if (is_resident(ni)) {
> -		struct folio *folio;
> +		struct folio *folio = NULL;
>   
>   		while ((folio = writeback_iter(mapping, wbc, folio, &err)))
>   			err = ntfs_resident_writepage(folio, wbc);
>
> ---
> base-commit: 099ef9ab9203dff327f2d61e44773f9acbc01f13
> change-id: 20260105-ntfs3-restore-null-folio-init-e3d7a7d6dd01
>
> Best regards,
> --
> Nathan Chancellor <nathan@kernel.org>

Queued for the next merge window, thanks.

Regards,
Konstantin


      reply	other threads:[~2026-01-16 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 19:17 Nathan Chancellor
2026-01-16 13:46 ` Konstantin Komarov [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=104e68d7-9b50-4318-ae64-8a22093c6e92@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ntfs3@lists.linux.dev \
    /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

all inboxes | Powered by JetHome®