From: syzbot <syzbot+baee8591f336cab0958b@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] general protection fault in bch2_snapshot_tree_oldest_subvol
Date: Fri, 04 Apr 2025 09:41:02 -0700 [thread overview]
Message-ID: <67f00b9e.050a0220.2dd465.0219.GAE@google.com> (raw)
In-Reply-To: <67eef48d.050a0220.9040b.0262.GAE@google.com>
syzbot has bisected this issue to:
commit 45f0e6c838e5d9af3f013adb4ba9aad3bcbcbe3b
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Fri Feb 7 06:33:01 2025 +0000
bcachefs: bch2_indirect_extent_missing_error() prints path, not just inode number
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10dea7cf980000
start commit: a2cc6ff5ec8f Merge tag 'firewire-updates-6.15' of git://gi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12dea7cf980000
console output: https://syzkaller.appspot.com/x/log.txt?x=14dea7cf980000
kernel config: https://syzkaller.appspot.com/x/.config?x=941480366fefa055
dashboard link: https://syzkaller.appspot.com/bug?extid=baee8591f336cab0958b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17062fb0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=131a0fb0580000
Reported-by: syzbot+baee8591f336cab0958b@syzkaller.appspotmail.com
Fixes: 45f0e6c838e5 ("bcachefs: bch2_indirect_extent_missing_error() prints path, not just inode number")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-04-04 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 20:50 [syzbot] [bcachefs?] general protection fault in bch2_snapshot_tree_oldest_subvol syzbot
2025-04-04 16:41 ` syzbot [this message]
2025-04-11 15:35 ` Charalampos Mitrodimas
2025-04-11 15:52 ` syzbot
2025-04-11 17:24 ` Kent Overstreet
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=67f00b9e.050a0220.2dd465.0219.GAE@google.com \
--to=syzbot+baee8591f336cab0958b@syzkaller.appspotmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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