Hello,
syzbot found the following issue on:
HEAD commit: 0ab06468cbd1 Linux 5.15.114
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17cc7369280000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9a2696a271d0eba
dashboard link:
https://syzkaller.appspot.com/bug?extid=345db7d28450eed314e4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/8ff3613d3f6b/disk-0ab06468.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/eebe2d8c6813/vmlinux-0ab06468.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/f30284c26197/Image-0ab06468.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+345db7...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 16538 at block/genhd.c:546 device_add_disk+0x5bc/0xaa0
Modules linked in:
CPU: 0 PID: 16538 Comm: syz-executor.1 Not tainted 5.15.114-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : device_add_disk+0x5bc/0xaa0
lr : device_add_disk+0x5b8/0xaa0 block/genhd.c:544
sp : ffff800020477b10
x29: ffff800020477b70 x28: dfff800000000000 x27: 0000000000700000
x26: ffff0000c049e2fc x25: 00000000ffffffea x24: ffff0000ca5e38a0
x23: 1fffe000194bc714 x22: 0000000000000001 x21: ffff0000ca5e3890
x20: 0000000000000007 x19: ffff0000ca5e3800 x18: 0000000000000001
x17: ff80800008335ea8 x16: ffff8000082ea770 x15: ffff8000089ba3d8
x14: ffff80000c01a6c0 x13: ffffffffffffffff x12: 0000000000040000
x11: 0000000000014294 x10: ffff80001dcbb000 x9 : ffff80000a821c58
x8 : 0000000000014295 x7 : 0000000000000000 x6 : ffff80000805cb6c
x5 : ffff0000d9ccfb20 x4 : 0000000000000000 x3 : ffff80000ab3b4ac
x2 : 0000000000000001 x1 : 0000000000000007 x0 : 0000000000000103
Call trace:
device_add_disk+0x5bc/0xaa0
add_disk include/linux/genhd.h:212 [inline]
loop_add+0x554/0x7ac drivers/block/loop.c:2430
loop_control_ioctl+0xec/0x62c drivers/block/loop.c:2545
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl fs/ioctl.c:860 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 458
hardirqs last enabled at (457): [<ffff8000088c87a8>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (458): [<ffff800011944c48>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (446): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (446): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (393): [<ffff8000081b573c>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (393): [<ffff8000081b573c>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (393): [<ffff8000081b573c>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
---[ end trace 0563d04fde2cc41a ]---
---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup