From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+2d7d0fbb5fb979113ff3@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernfs?] possible deadlock in kernfs_remove
Date: Tue, 5 Aug 2025 10:27:52 +0800 [thread overview]
Message-ID: <20250805022753.3917-1-hdanton@sina.com> (raw)
In-Reply-To: <6890f71a.050a0220.7f033.0010.GAE@google.com>
> Date: Mon, 04 Aug 2025 11:08:26 -0700 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 759dfc7d04ba netlink: avoid infinite retry looping in netl..
> git tree: net
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=11332f82580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ac0888b9ad46cd69
> dashboard link: https://syzkaller.appspot.com/bug?extid=2d7d0fbb5fb979113ff3
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1136d9bc580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1536d9bc580000
#syz test upstream master
--- x/fs/kernfs/mount.c
+++ y/fs/kernfs/mount.c
@@ -303,9 +303,7 @@ static int kernfs_fill_super(struct supe
sb->s_shrink->seeks = 0;
/* get root inode, initialize and unlock it */
- down_read(&kf_root->kernfs_rwsem);
inode = kernfs_get_inode(sb, info->root->kn);
- up_read(&kf_root->kernfs_rwsem);
if (!inode) {
pr_debug("kernfs: could not get root inode\n");
return -ENOMEM;
--
next prev parent reply other threads:[~2025-08-05 2:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 18:08 syzbot
2025-08-05 2:27 ` Hillf Danton [this message]
2025-08-05 3:02 ` syzbot
2025-08-07 11:41 ` Edward Adam Davis
2025-08-07 14:02 ` syzbot
2025-08-07 14:15 ` Edward Adam Davis
2025-08-07 14:45 ` syzbot
2025-10-28 15:04 ` syzbot
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=20250805022753.3917-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2d7d0fbb5fb979113ff3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®