From: Jan Kara <jack@suse.cz>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH -next] fanotify: Fix the checks in fanotify_fsid_equal
Date: Mon, 30 Mar 2020 12:40:45 +0200 [thread overview]
Message-ID: <20200330104045.GA26544@quack2.suse.cz> (raw)
In-Reply-To: <20200327171030.30625-1-natechancellor@gmail.com>
On Fri 27-03-20 10:10:30, Nathan Chancellor wrote:
> Clang warns:
>
> fs/notify/fanotify/fanotify.c:28:23: warning: self-comparison always
> evaluates to true [-Wtautological-compare]
> return fsid1->val[0] == fsid1->val[0] && fsid2->val[1] == fsid2->val[1];
> ^
> fs/notify/fanotify/fanotify.c:28:57: warning: self-comparison always
> evaluates to true [-Wtautological-compare]
> return fsid1->val[0] == fsid1->val[0] && fsid2->val[1] == fsid2->val[1];
> ^
> 2 warnings generated.
>
> The intention was clearly to compare val[0] and val[1] in the two
> different fsid structs. Fix it otherwise this function always returns
> true.
>
> Fixes: afc894c784c8 ("fanotify: Store fanotify handles differently")
> Link: https://github.com/ClangBuiltLinux/linux/issues/952
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
Thanks for the fix! That's a good catch that would have been pain to debug!
I've applied it to my tree.
Honza
> ---
> fs/notify/fanotify/fanotify.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/notify/fanotify/fanotify.c b/fs/notify/fanotify/fanotify.c
> index 7a889da1ee12..cb54ecdb3fb9 100644
> --- a/fs/notify/fanotify/fanotify.c
> +++ b/fs/notify/fanotify/fanotify.c
> @@ -25,7 +25,7 @@ static bool fanotify_path_equal(struct path *p1, struct path *p2)
> static inline bool fanotify_fsid_equal(__kernel_fsid_t *fsid1,
> __kernel_fsid_t *fsid2)
> {
> - return fsid1->val[0] == fsid1->val[0] && fsid2->val[1] == fsid2->val[1];
> + return fsid1->val[0] == fsid2->val[0] && fsid1->val[1] == fsid2->val[1];
> }
>
> static bool fanotify_fh_equal(struct fanotify_fh *fh1,
> --
> 2.26.0
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-03-30 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 17:10 [PATCH -next] fanotify: Fix the checks in fanotify_fsid_equal Nathan Chancellor
2020-03-27 17:26 ` Nick Desaulniers
2020-03-28 9:15 ` Amir Goldstein
2020-03-30 10:40 ` Jan Kara [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=20200330104045.GA26544@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.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