From: syzbot <syzbot+cee29f5a48caf10cd475@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, eadavis@qq.com, fdmanana@suse.com,
josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, quwenruo.btrfs@gmx.com,
syzkaller-bugs@googlegroups.com, wqu@suse.com
Subject: Re: [syzbot] [btrfs?] general protection fault in getname_kernel (2)
Date: Wed, 09 Oct 2024 21:30:03 -0700 [thread overview]
Message-ID: <6707584b.050a0220.67064.0059.GAE@google.com> (raw)
In-Reply-To: <670689a8.050a0220.67064.0046.GAE@google.com>
syzbot has bisected this issue to:
commit b4b3fb6c00f37a9da91022adcd83555bc339e044
Author: Qu Wenruo <wqu@suse.com>
Date: Tue Sep 24 04:57:07 2024 +0000
btrfs: canonicalize the device path before adding it
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15744f07980000
start commit: 33ce24234fca Add linux-next specific files for 20241008
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17744f07980000
console output: https://syzkaller.appspot.com/x/log.txt?x=13744f07980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4750ca93740b938d
dashboard link: https://syzkaller.appspot.com/bug?extid=cee29f5a48caf10cd475
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160ce327980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15ea7707980000
Reported-by: syzbot+cee29f5a48caf10cd475@syzkaller.appspotmail.com
Fixes: b4b3fb6c00f3 ("btrfs: canonicalize the device path before adding it")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-10-10 4:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 13:48 [syzbot] [btrfs?] general protection fault in getname_kernel (2) syzbot
2024-10-09 14:33 ` Edward Adam Davis
2024-10-09 18:51 ` [syzbot] " syzbot
2024-10-09 23:21 ` Qu Wenruo
2024-10-10 0:29 ` syzbot
2024-10-10 2:26 ` Qu Wenruo
2024-10-10 3:02 ` syzbot
2024-10-10 4:30 ` syzbot [this message]
2024-10-10 4:54 ` Qu Wenruo
2024-10-10 5:37 ` 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=6707584b.050a0220.67064.0059.GAE@google.com \
--to=syzbot+cee29f5a48caf10cd475@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=eadavis@qq.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wqu@suse.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