mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: trix@redhat.com
Cc: konishi.ryusuke@gmail.com, ndesaulniers@google.com,
	linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH] nilfs2: move initialization of nr_dirty to decl
Date: Thu, 17 Mar 2022 11:12:14 -0700	[thread overview]
Message-ID: <YjN5/h+0fR6Ph/5H@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20220317175043.1972081-1-trix@redhat.com>

Hi Tom,

On Thu, Mar 17, 2022 at 10:50:43AM -0700, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
> 
> On clang build there is this error
> inode.c:227:13: error: variable 'nr_dirty' is
>   used uninitialized whenever 'if' condition is false
>         } else if (ret) {
>                    ^~~
> 
> In nilfs_dirty_folio(), if the call to
> filemap_dirty_folio() fails and there
> are no buffers, nr_dirty will be uninitialized.
> Move the initialization out of the buffer
> block and to the decl.
> 
> Signed-off-by: Tom Rix <trix@redhat.com>

This has been fixed in next-20220317:

https://git.kernel.org/next/linux-next/c/af7afdc7bbbe60cb6ce51a86b022d647e1a72717

Cheers,
Nathan

> ---
>  fs/nilfs2/inode.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/fs/nilfs2/inode.c b/fs/nilfs2/inode.c
> index c1219c0678a57..01e58b65c9384 100644
> --- a/fs/nilfs2/inode.c
> +++ b/fs/nilfs2/inode.c
> @@ -204,7 +204,7 @@ static bool nilfs_dirty_folio(struct address_space *mapping,
>  {
>  	struct inode *inode = mapping->host;
>  	struct buffer_head *head;
> -	unsigned int nr_dirty;
> +	unsigned int nr_dirty = 0;
>  	bool ret = filemap_dirty_folio(mapping, folio);
>  
>  	/*
> @@ -214,8 +214,6 @@ static bool nilfs_dirty_folio(struct address_space *mapping,
>  	head = folio_buffers(folio);
>  	if (head) {
>  		struct buffer_head *bh = head;
> -
> -		nr_dirty = 0;
>  		do {
>  			/* Do not mark hole blocks dirty */
>  			if (buffer_dirty(bh) || !buffer_mapped(bh))
> -- 
> 2.26.3
> 

      reply	other threads:[~2022-03-17 18:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 17:50 trix
2022-03-17 18:12 ` Nathan Chancellor [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=YjN5/h+0fR6Ph/5H@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=ndesaulniers@google.com \
    --cc=trix@redhat.com \
    /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®