Hello,
syzbot found the following issue on:
HEAD commit: 1a8763b93150 Linux 6.1.188
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16335315580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=7e5b41322189806a
dashboard link:
https://syzkaller.appspot.com/bug?extid=5cf657607a92c6749595
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/79d582e9ec4f/disk-1a8763b9.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/70e43b512b19/vmlinux-1a8763b9.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/7107d5b60093/Image-1a8763b9.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+5cf657...@syzkaller.appspotmail.com
syz.7.520: attempt to access beyond end of device
loop7: rw=2049, sector=18, nr_sectors = 2 limit=1
Buffer I/O error on dev loop7, logical block 9, lost async page write
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7084 at fs/buffer.c:1081 mark_buffer_dirty+0x328/0x5c0 fs/buffer.c:1081
Modules linked in:
CPU: 1 PID: 7084 Comm: syz.7.520 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2026
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : mark_buffer_dirty+0x328/0x5c0 fs/buffer.c:1081
lr : mark_buffer_dirty+0x328/0x5c0 fs/buffer.c:1081
sp : ffff800021fd7680
x29: ffff800021fd7680 x28: 0000000000000000 x27: dfff800000000000
x26: 0000000000000008 x25: 0000000000000000 x24: ffff0000fb0623a0
x23: ffff0000cdb6a300 x22: ffff0000fb0623c8 x21: 0000000000000000
x20: 000000000000041a x19: ffff0000fb0623a0 x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000082f2d78 x15: 000000000004ffff
x14: 0000000000000001 x13: 1fffe0001f60c474 x12: 0000000000080000
x11: 00000000000035a2 x10: ffff80002a121000 x9 : ffff800008a9ffe8
x8 : 00000000000035a3 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff800018881310 x4 : 0000000000000008 x3 : ffff800008a9fcf0
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
mark_buffer_dirty+0x328/0x5c0 fs/buffer.c:1081
minix_new_inode+0x28c/0x4a8 fs/minix/bitmap.c:249
minix_mknod+0xc4/0x194 fs/minix/namei.c:45
minix_create+0x38/0x4c fs/minix/namei.c:71
lookup_open fs/namei.c:3533 [inline]
open_last_lookups fs/namei.c:3601 [inline]
path_openat+0xda8/0x27a0 fs/namei.c:3831
do_filp_open+0x198/0x38c fs/namei.c:3861
do_sys_openat2+0x134/0x3fc fs/open.c:1320
do_sys_open fs/open.c:1336 [inline]
__do_sys_openat fs/open.c:1352 [inline]
__se_sys_openat fs/open.c:1347 [inline]
__arm64_sys_openat+0x11c/0x150 fs/open.c:1347
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 6028
hardirqs last enabled at (6027): [<ffff800011c9da4c>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (6027): [<ffff800011c9da4c>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (6028): [<ffff800011bb2834>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (5974): [<ffff800008031254>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (5972): [<ffff800008031220>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
syz.7.520: attempt to access beyond end of device
loop7: rw=2049, sector=16, nr_sectors = 2 limit=1
Buffer I/O error on dev loop7, logical block 8, lost async page write
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup