From: syzbot <syzbot+f4f84b57a01d6b8364ad@syzkaller.appspotmail.com>
To: axboe@kernel.dk, brauner@kernel.org, hare@suse.de,
hirofumi@mail.parknet.co.jp, linkinjeon@kernel.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mcgrof@kernel.org,
sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [exfat?] kernel BUG in folio_set_bh
Date: Thu, 03 Jul 2025 01:07:02 -0700 [thread overview]
Message-ID: <68663a26.a70a0220.5d25f.0856.GAE@google.com> (raw)
In-Reply-To: <6865e87a.a70a0220.2b31f5.000a.GAE@google.com>
syzbot has bisected this issue to:
commit 47dd67532303803a87f43195e088b3b4bcf0454d
Author: Luis Chamberlain <mcgrof@kernel.org>
Date: Fri Feb 21 22:38:22 2025 +0000
block/bdev: lift block size restrictions to 64k
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15ec33d4580000
start commit: 50c8770a42fa Add linux-next specific files for 20250702
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17ec33d4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=13ec33d4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d831c9dfe03f77ec
dashboard link: https://syzkaller.appspot.com/bug?extid=f4f84b57a01d6b8364ad
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c93770580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1001aebc580000
Reported-by: syzbot+f4f84b57a01d6b8364ad@syzkaller.appspotmail.com
Fixes: 47dd67532303 ("block/bdev: lift block size restrictions to 64k")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-07-03 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 2:18 [syzbot] [exfat?] kernel BUG in folio_set_bh syzbot
2025-07-03 8:07 ` syzbot [this message]
2025-07-05 2:17 ` Luis Chamberlain
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=68663a26.a70a0220.5d25f.0856.GAE@google.com \
--to=syzbot+f4f84b57a01d6b8364ad@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=hare@suse.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linkinjeon@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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 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).