From: Jan Kara <jack@suse.cz>
To: Jules Irenge <jbi.octave@gmail.com>
Cc: linux-kernel@vger.kernel.org, boqun.feng@gmail.com,
Jan Kara <jack@suse.cz>, Amir Goldstein <amir73il@gmail.com>,
"open list:FSNOTIFY: FILESYSTEM NOTIFICATION INFRASTRUCTURE"
<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2] fsnotify: Add missing annotation for fsnotify_finish_user_wait() and for fsnotify_prepare_user_wait()
Date: Wed, 15 Apr 2020 11:45:16 +0200 [thread overview]
Message-ID: <20200415094516.GA6126@quack2.suse.cz> (raw)
In-Reply-To: <20200413214240.15245-1-jbi.octave@gmail.com>
On Mon 13-04-20 22:42:40, Jules Irenge wrote:
> Sparse reports warnings at fsnotify_prepare_user_wait()
> and at fsnotify_finish_user_wait()
>
> warning: context imbalance in fsnotify_finish_user_wait()
> - wrong count at exit
> warning: context imbalance in fsnotify_prepare_user_wait()
> - unexpected unlock
>
> The root cause is the missing annotation at fsnotify_finish_user_wait()
> and at fsnotify_prepare_user_wait()
> fsnotify_prepare_user_wait() has an extra annotation __release()
> that only tell Sparse and not GCC to shutdown the warning
>
> Add the missing __acquires(&fsnotify_mark_srcu) annotation
> Add the missing __releases(&fsnotify_mark_srcu) annotation
> Add the __release(&fsnotify_mark_srcu) annotation.
Thanks for the patch. I've added it to my tree.
Honza
>
> Signed-off-by: Jules Irenge <jbi.octave@gmail.com>
> ---
> changes since v2
> -include annotations for fsnotify_prepare_user_wait()
>
> fs/notify/mark.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/fs/notify/mark.c b/fs/notify/mark.c
> index 1d96216dffd1..8387937b9d01 100644
> --- a/fs/notify/mark.c
> +++ b/fs/notify/mark.c
> @@ -325,13 +325,16 @@ static void fsnotify_put_mark_wake(struct fsnotify_mark *mark)
> }
>
> bool fsnotify_prepare_user_wait(struct fsnotify_iter_info *iter_info)
> + __releases(&fsnotify_mark_srcu)
> {
> int type;
>
> fsnotify_foreach_obj_type(type) {
> /* This can fail if mark is being removed */
> - if (!fsnotify_get_mark_safe(iter_info->marks[type]))
> + if (!fsnotify_get_mark_safe(iter_info->marks[type])) {
> + __release(&fsnotify_mark_srcu);
> goto fail;
> + }
> }
>
> /*
> @@ -350,6 +353,7 @@ bool fsnotify_prepare_user_wait(struct fsnotify_iter_info *iter_info)
> }
>
> void fsnotify_finish_user_wait(struct fsnotify_iter_info *iter_info)
> + __acquires(&fsnotify_mark_srcu)
> {
> int type;
>
> --
> 2.24.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2020-04-15 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 21:42 Jules Irenge
2020-04-15 9:45 ` 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=20200415094516.GA6126@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=jbi.octave@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®