From: Greg KH <gregkh@linuxfoundation.org>
To: Chengming Zhou <zhouchengming@bytedance.com>
Cc: tj@kernel.org, linux-kernel@vger.kernel.org,
syzbot+2fdf66e68f5f882c1074@syzkaller.appspotmail.com
Subject: Re: [PATCH] fs/kernfs: Fix lockdep warning in kernfs_active()
Date: Thu, 10 Nov 2022 19:00:52 +0100 [thread overview]
Message-ID: <Y208VBO9cZ5VL88m@kroah.com> (raw)
In-Reply-To: <20221109120415.55759-1-zhouchengming@bytedance.com>
On Wed, Nov 09, 2022 at 08:04:15PM +0800, Chengming Zhou wrote:
> syzbot found a lockdep warning in kernfs_find_and_get_node_by_id(),
> bisected to the commit c25491747b21 ("kernfs: Add KERNFS_REMOVING flags"),
> which didn't hold kernfs_rwsem before call kernfs_active(kn).
>
> Since kernfs_find_and_get_node_by_id() doesn't have to get active count
> of kn, only need to get a stable refcount of kn, so it should be enough
> to just check kn has been KERNFS_ACTIVATED.
>
> Reported-by: syzbot+2fdf66e68f5f882c1074@syzkaller.appspotmail.com
> Fixes: c25491747b21 ("kernfs: Add KERNFS_REMOVING flags")
> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
> ---
> fs/kernfs/dir.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/fs/kernfs/dir.c b/fs/kernfs/dir.c
> index 6acd9c3d4cff..08f0f1570cd7 100644
> --- a/fs/kernfs/dir.c
> +++ b/fs/kernfs/dir.c
> @@ -705,7 +705,13 @@ struct kernfs_node *kernfs_find_and_get_node_by_id(struct kernfs_root *root,
> goto err_unlock;
> }
>
> - if (unlikely(!kernfs_active(kn) || !atomic_inc_not_zero(&kn->count)))
> + /*
> + * ACTIVATED is protected with kernfs_mutex but it was clear when
> + * @kn was added to idr and we just wanna see it set. No need to
> + * grab kernfs_mutex.
> + */
> + if (unlikely(!(kn->flags & KERNFS_ACTIVATED) ||
> + !atomic_inc_not_zero(&kn->count)))
> goto err_unlock;
>
> spin_unlock(&kernfs_idr_lock);
> --
> 2.37.2
>
Shouldn't:
https://lore.kernel.org/r/Y0SwqBsZ9BMmZv6x@slm.duckdns.org fix this
instead?
next prev parent reply other threads:[~2022-11-10 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 16:11 [syzbot] WARNING in kernfs_find_and_get_node_by_id syzbot
2022-11-07 12:07 ` Chengming Zhou
2022-11-09 12:04 ` [PATCH] fs/kernfs: Fix lockdep warning in kernfs_active() Chengming Zhou
2022-11-09 15:46 ` Tejun Heo
2022-11-10 18:00 ` Greg KH [this message]
2022-11-10 18:11 ` Tejun Heo
2022-11-10 18:20 ` Greg KH
2022-11-10 18:28 ` Tejun Heo
2022-11-23 18:30 ` Greg KH
2022-11-23 18:35 ` Tejun Heo
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=Y208VBO9cZ5VL88m@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2fdf66e68f5f882c1074@syzkaller.appspotmail.com \
--cc=tj@kernel.org \
--cc=zhouchengming@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.