From: syzbot <syzbot+5a195884ee3ad761db4e@syzkaller.appspotmail.com>
To: casey@schaufler-ca.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, paul@paul-moore.com,
reiserfs-devel@vger.kernel.org, roberto.sassu@huawei.com,
syzkaller-bugs@googlegroups.com, zohar@linux.ibm.com
Subject: Re: [syzbot] [reiserfs?] [overlayfs?] WARNING: locking bug in take_dentry_name_snapshot
Date: Fri, 19 May 2023 13:56:23 -0700 [thread overview]
Message-ID: <00000000000058b12b05fc122703@google.com> (raw)
In-Reply-To: <0000000000001b987605f47b72d3@google.com>
syzbot suspects this issue was fixed by commit:
commit 52ca4b6435a493e47aaa98e7345e19e1e8710b13
Author: Roberto Sassu <roberto.sassu@huawei.com>
Date: Tue Mar 14 08:17:15 2023 +0000
reiserfs: Switch to security_inode_init_security()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=121dea5a280000
start commit: 4bdec23f971b Merge tag 'hwmon-for-v6.3-rc4' of git://git.k..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ea09b0836073ee4
dashboard link: https://syzkaller.appspot.com/bug?extid=5a195884ee3ad761db4e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1277fb1ec80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12543651c80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: reiserfs: Switch to security_inode_init_security()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2023-05-19 20:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000001b987605f47b72d3@google.com>]
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=00000000000058b12b05fc122703@google.com \
--to=syzbot+5a195884ee3ad761db4e@syzkaller.appspotmail.com \
--cc=casey@schaufler-ca.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=paul@paul-moore.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zohar@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).