From: Keith Busch <kbusch@kernel.org>
To: syzbot <syzbot+8df17e797225d69050d4@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, martin.petersen@oracle.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] general protection fault in bio_seg_gap
Date: Fri, 14 Nov 2025 11:01:20 -0700 [thread overview]
Message-ID: <aRducE3vsSWcznMs@kbusch-mbp> (raw)
In-Reply-To: <6916bd0e.a70a0220.3124cb.0046.GAE@google.com>
On Thu, Nov 13, 2025 at 09:24:30PM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: ab40c92c74c6 Add linux-next specific files for 20251110
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=12e2317c580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=b4c0e7075df4bf51
> dashboard link: https://syzkaller.appspot.com/bug?extid=8df17e797225d69050d4
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11527084580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13e1b412580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/63d584f3f4ab/disk-ab40c92c.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/4bb564de81d2/vmlinux-ab40c92c.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/704d37065029/bzImage-ab40c92c.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/c9f9c8e46d00/mount_0.gz
> fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=14ec87cd980000)
>
> The issue was bisected to:
>
> commit 2f6b2565d43cdb5087cac23d530cca84aa3d897e
> Author: Keith Busch <kbusch@kernel.org>
> Date: Tue Oct 14 15:04:55 2025 +0000
>
> block: accumulate memory segment gaps per bio
#syz fix: block: fix merging data-less bios
prev parent reply other threads:[~2025-11-14 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 5:24 [syzbot] [block?] general protection fault in bio_seg_gap syzbot
2025-11-14 18:01 ` Keith Busch [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=aRducE3vsSWcznMs@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=syzbot+8df17e797225d69050d4@syzkaller.appspotmail.com \
--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