From: syzbot <syzbot+32415e0466b02533303c@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?] INFO: task hung in bch2_page_fault
Date: Fri, 20 Jun 2025 18:50:01 -0700 [thread overview]
Message-ID: <68560fc9.a00a0220.137b3.005c.GAE@google.com> (raw)
In-Reply-To: <675cb812.050a0220.37aaf.00b6.GAE@google.com>
syzbot has bisected this issue to:
commit 8b1f46bff38f075b8d4071e7ac1edecb441fd53c
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sun Dec 29 00:57:04 2024 +0000
bcachefs: Dropped superblock write is no longer a fatal error
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=140d530c580000
start commit: 9afe652958c3 Merge tag 'x86_urgent_for_6.16-rc3' of git://..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=160d530c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=120d530c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a237c32900fc479
dashboard link: https://syzkaller.appspot.com/bug?extid=32415e0466b02533303c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=130d790c580000
Reported-by: syzbot+32415e0466b02533303c@syzkaller.appspotmail.com
Fixes: 8b1f46bff38f ("bcachefs: Dropped superblock write is no longer a fatal error")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-06-21 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 22:41 [syzbot] [bcachefs?] INFO: task hung in bch2_page_fault syzbot
2025-06-17 16:52 ` syzbot
2025-08-08 5:40 ` Alan Huang
2025-06-21 1:50 ` syzbot [this message]
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=68560fc9.a00a0220.137b3.005c.GAE@google.com \
--to=syzbot+32415e0466b02533303c@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;
as well as URLs for NNTP newsgroup(s).