From: syzbot <syzbot+f6e8174215573a84b797@syzkaller.appspotmail.com>
To: activprithvi@gmail.com, hch@lst.de, jlbec@evilplan.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] possible deadlock in __configfs_open_file
Date: Thu, 08 Jan 2026 09:58:02 -0800 [thread overview]
Message-ID: <695ff02a.050a0220.1c677c.03a4.GAE@google.com> (raw)
In-Reply-To: <20260108173211.248566-1-activprithvi@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+f6e8174215573a84b797@syzkaller.appspotmail.com
Tested-by: syzbot+f6e8174215573a84b797@syzkaller.appspotmail.com
Tested on:
commit: 3a866087 Linux 6.18-rc1
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=101c119a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e854293d7f44b5a5
dashboard link: https://syzkaller.appspot.com/bug?extid=f6e8174215573a84b797
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=11859f92580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-01-08 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 9:16 [syzbot] [fs?] possible deadlock in __configfs_open_file syzbot
2026-01-08 17:32 ` Syzbot test for fixing recursive locking " Prithvi Tambewagh
2026-01-08 17:58 ` syzbot [this message]
2026-01-21 15:02 ` Testing for v2: configfs: add lock class key to struct configfs_fragment for frag_sem Prithvi Tambewagh
2026-01-21 15:19 ` [syzbot] [fs?] possible deadlock in __configfs_open_file 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=695ff02a.050a0220.1c677c.03a4.GAE@google.com \
--to=syzbot+f6e8174215573a84b797@syzkaller.appspotmail.com \
--cc=activprithvi@gmail.com \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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