From: Jan Kara <jack@suse.cz>
To: ZhangXiaoxu <zhangxiaoxu5@huawei.com>
Cc: jack@suse.cz, amir73il@gmail.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] inotify: Fix fsnotify_mark refcount leak in inotify_update_existing_watch()
Date: Mon, 11 Mar 2019 10:13:38 +0100 [thread overview]
Message-ID: <20190311091338.GC11553@quack2.suse.cz> (raw)
In-Reply-To: <1551489452-30199-1-git-send-email-zhangxiaoxu5@huawei.com>
On Sat 02-03-19 09:17:32, ZhangXiaoxu wrote:
> Commit 4d97f7d53da7dc83 ("inotify: Add flag IN_MASK_CREATE for
> inotify_add_watch()") forgot to call fsnotify_put_mark() with
> IN_MASK_CREATE after fsnotify_find_mark()
>
> Fixes: 4d97f7d53da7dc83 ("inotify: Add flag IN_MASK_CREATE for inotify_add_watch()")
> Signed-off-by: ZhangXiaoxu <zhangxiaoxu5@huawei.com>
Thanks for the patch! I've added it to my tree.
Honza
> ---
> fs/notify/inotify/inotify_user.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/fs/notify/inotify/inotify_user.c b/fs/notify/inotify/inotify_user.c
> index 798f125..3b7b8e9 100644
> --- a/fs/notify/inotify/inotify_user.c
> +++ b/fs/notify/inotify/inotify_user.c
> @@ -519,8 +519,10 @@ static int inotify_update_existing_watch(struct fsnotify_group *group,
> fsn_mark = fsnotify_find_mark(&inode->i_fsnotify_marks, group);
> if (!fsn_mark)
> return -ENOENT;
> - else if (create)
> - return -EEXIST;
> + else if (create) {
> + ret = -EEXIST;
> + goto out;
> + }
>
> i_mark = container_of(fsn_mark, struct inotify_inode_mark, fsn_mark);
>
> @@ -548,6 +550,7 @@ static int inotify_update_existing_watch(struct fsnotify_group *group,
> /* return the wd */
> ret = i_mark->wd;
>
> +out:
> /* match the get from fsnotify_find_mark() */
> fsnotify_put_mark(fsn_mark);
>
> --
> 2.7.4
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2019-03-11 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 1:17 [PATCH] inotify: Fix fsnotify_mark refcount leak in inotify_update_existing_watch() ZhangXiaoxu
2019-03-04 1:10 ` zhangxiaoxu (A)
2019-03-11 7:48 ` zhangxiaoxu (A)
2019-03-11 8:36 ` Amir Goldstein
2019-03-11 9:13 ` 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=20190311091338.GC11553@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zhangxiaoxu5@huawei.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;
as well as URLs for NNTP newsgroup(s).