mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Maxim Korotkov <korotkov.maxim.s@gmail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Jens Axboe <axboe@fb.com>, Tejun Heo <tj@kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	lvc-project@linuxtesting.org
Subject: Re: [PATCH] writeback: fix call of incorrect macro
Date: Thu, 26 Jan 2023 14:52:58 +0100	[thread overview]
Message-ID: <20230126135258.zpvyfxc2ffhzzsnx@quack3> (raw)
In-Reply-To: <20230119104443.3002-1-korotkov.maxim.s@gmail.com>

On Thu 19-01-23 13:44:43, Maxim Korotkov wrote:
>  the variable 'history' is of type u16, it may be an error 
>  that the hweight32 macro was used for it 
>  I guess macro hweight16 should be used
> 
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
> 
> Fixes: 2a81490811d0 ("writeback: implement foreign cgroup inode detection")
> Signed-off-by: Maxim Korotkov <korotkov.maxim.s@gmail.com>

Looks good to me, although it is mostly a theoretical issue - I don't see
how hweight32 could do any harm here. Anyway, feel free to add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  fs/fs-writeback.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index 6fba5a52127b..fc16123b2405 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -829,7 +829,7 @@ void wbc_detach_inode(struct writeback_control *wbc)
>  		 * is okay.  The main goal is avoiding keeping an inode on
>  		 * the wrong wb for an extended period of time.
>  		 */
> -		if (hweight32(history) > WB_FRN_HIST_THR_SLOTS)
> +		if (hweight16(history) > WB_FRN_HIST_THR_SLOTS)
>  			inode_switch_wbs(inode, max_id);
>  	}
>  
> -- 
> 2.37.2
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2023-01-26 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 10:44 Maxim Korotkov
2023-01-26 13:52 ` Jan Kara [this message]
2023-04-12 14:31   ` Maxim Korotkov
2023-04-28 13:09     ` Jan Kara
2023-04-28 16:42 ` Jens Axboe

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=20230126135258.zpvyfxc2ffhzzsnx@quack3 \
    --to=jack@suse.cz \
    --cc=axboe@fb.com \
    --cc=korotkov.maxim.s@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=tj@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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®