From: syzbot <syzbot+ac00e7bf7ac8c91af921@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hch@infradead.org, kbusch@kernel.org,
kbusch@meta.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] WARNING in blk_validate_limits
Date: Sat, 29 Aug 2026 22:08:27 -0700 [thread overview]
Message-ID: <6a93bacb.08e933ee.dbf97.00f9.GAE@google.com> (raw)
In-Reply-To: <6a778d36.01d0871a.3a0d52.006f.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: e30626823a40 Add linux-next specific files for 20260828
git tree: linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=157e7d79580000
kernel config: https://syzkaller.appspot.com/x/.config?x=da8932b2925a9804
dashboard link: https://syzkaller.appspot.com/bug?extid=ac00e7bf7ac8c91af921
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16936e25580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=179fc379580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f3d0d809c004/disk-e3062682.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/14efbbb42757/vmlinux-e3062682.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0919b1002ace/bzImage-e3062682.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/4f0c60a63a72/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=12936e25580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ac00e7bf7ac8c91af921@syzkaller.appspotmail.com
F2FS-fs (loop0): f2fs_disable_checkpoint finishes, err:0
F2FS-fs (loop0): Mounted with checkpoint version = 48b305e6
fscrypt: AES-256-XTS using blk-crypto-fallback
------------[ cut here ]------------
lim->dma_alignment > PAGE_SIZE
WARNING: block/blk-settings.c:497 at blk_validate_limits+0x1676/0x2270 block/blk-settings.c:497, CPU#1: syz-executor215/5627
Modules linked in:
CPU: 1 UID: 0 PID: 5627 Comm: syz-executor215 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:blk_validate_limits+0x1676/0x2270 block/blk-settings.c:497
Code: e8 cf da 0b fd 90 0f 0b 90 eb 8f e8 c4 da 0b fd 90 0f 0b 90 eb 84 e8 b9 da 0b fd 90 0f 0b 90 e9 76 ff ff ff e8 ab da 0b fd 90 <0f> 0b 90 e9 68 ff ff ff e8 9d da 0b fd 90 0f 0b 90 e9 81 00 00 00
RSP: 0018:ffffc900038dee60 EFLAGS: 00010293
RAX: ffffffff84bbe625 RBX: ffffc900038df0f0 RCX: ffff888076f99f40
RDX: 0000000000000000 RSI: 00000000ffffffff RDI: 0000000000001000
RBP: 00000000ffffffff R08: ffff88806ec9427f R09: 1ffff1100dd9284f
R10: dffffc0000000000 R11: ffffed100dd92850 R12: ffffc900038df040
R13: dffffc0000000000 R14: 1ffff9200071be1e R15: dffffc0000000000
FS: 000055557ce9e400(0000) GS:ffff888124dd6000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000072708000 CR4: 00000000003526f0
Call Trace:
<TASK>
queue_limits_commit_update+0x87/0x390 block/blk-settings.c:552
loop_configure+0x7f1/0xdc0 drivers/block/loop.c:1086
lo_ioctl+0xae0/0x2010 drivers/block/loop.c:1564
blkdev_ioctl+0x5e3/0x740 block/ioctl.c:798
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1351d03669
Code: c0 79 93 eb d5 48 8d 7c 1d 00 eb 99 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 d8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd20598c38 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1351d03669
RDX: 00002000000005c0 RSI: 0000000000004c0a RDI: 0000000000000004
RBP: 0000000000000001 R08: 000055557ce9f580 R09: 000055557ce9f580
R10: 0000200000000600 R11: 0000000000000246 R12: 00007ffd20598c60
R13: 0000000000000002 R14: 431bde82d7b634db R15: 00007f1351d6204b
</TASK>
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
prev parent reply other threads:[~2026-08-30 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 20:10 syzbot
2026-08-30 5:08 ` 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=6a93bacb.08e933ee.dbf97.00f9.GAE@google.com \
--to=syzbot+ac00e7bf7ac8c91af921@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@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
all inboxes | Powered by JetHome®