From: syzbot <syzbot+e37a1730d63d207fe403@syzkaller.appspotmail.com>
To: bfoster@redhat.com, gregkh@linuxfoundation.org,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tj@kernel.org
Subject: Re: [syzbot] [kernfs?] general protection fault in kernfs_dop_revalidate
Date: Sun, 08 Jun 2025 20:11:02 -0700 [thread overview]
Message-ID: <684650c6.050a0220.d8705.0018.GAE@google.com> (raw)
In-Reply-To: <6745a8df.050a0220.1286eb.0015.GAE@google.com>
syzbot has bisected this issue to:
commit f7643bc9749f270d487c32dc35b578575bf1adb0
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Wed Apr 17 05:26:02 2024 +0000
bcachefs: make btree read errors silent during scan
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17abb20c580000
start commit: 28eb75e178d3 Merge tag 'drm-next-2024-11-21' of https://gi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=146bb20c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=106bb20c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=402159daa216c89d
dashboard link: https://syzkaller.appspot.com/bug?extid=e37a1730d63d207fe403
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=163706e8580000
Reported-by: syzbot+e37a1730d63d207fe403@syzkaller.appspotmail.com
Fixes: f7643bc9749f ("bcachefs: make btree read errors silent during scan")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-09 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 10:54 [syzbot] [kernfs?] [bcachefs?] general protection fault in kernfs_dop_revalidate syzbot
2025-06-09 3:11 ` syzbot [this message]
2025-06-09 3:18 ` [syzbot] [kernfs?] " Kent Overstreet
2025-06-09 7:02 ` Aleksandr Nogikh
2025-06-09 3:13 ` [syzbot] [kernfs?] [bcachefs?] " 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=684650c6.050a0220.d8705.0018.GAE@google.com \
--to=syzbot+e37a1730d63d207fe403@syzkaller.appspotmail.com \
--cc=bfoster@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.