From: syzbot <syzbot+2cca5ef7e5ed862c0799@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, brauner@kernel.org, jack@suse.cz,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mjguzik@gmail.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ext4?] WARNING in inode_set_cached_link
Date: Sat, 08 Feb 2025 10:13:07 -0800 [thread overview]
Message-ID: <67a79eb3.050a0220.3d72c.002b.GAE@google.com> (raw)
In-Reply-To: <67a4eae3.050a0220.65602.0000.GAE@google.com>
syzbot has bisected this issue to:
commit 6408a56623761f969537b421d99f045a4cc955b9
Author: Mateusz Guzik <mjguzik@gmail.com>
Date: Tue Feb 4 21:32:07 2025 +0000
vfs: sanity check the length passed to inode_set_cached_link()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=152ffca4580000
start commit: 808eb958781e Add linux-next specific files for 20250206
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=172ffca4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=132ffca4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=88b25e5d30d576e4
dashboard link: https://syzkaller.appspot.com/bug?extid=2cca5ef7e5ed862c0799
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=161241b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ee80e4580000
Reported-by: syzbot+2cca5ef7e5ed862c0799@syzkaller.appspotmail.com
Fixes: 6408a5662376 ("vfs: sanity check the length passed to inode_set_cached_link()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-02-08 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 17:01 [syzbot] [ext4?] WARNING in inode_set_cached_link syzbot
2025-02-08 18:13 ` syzbot [this message]
2025-02-08 18:23 ` Mateusz Guzik
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=67a79eb3.050a0220.3d72c.002b.GAE@google.com \
--to=syzbot+2cca5ef7e5ed862c0799@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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