Hello,
syzbot found the following issue on:
HEAD commit: 3dea0e7f549e Linux 5.15.186
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16736a8c580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=fe91feccd8127a59
dashboard link:
https://syzkaller.appspot.com/bug?extid=4d61e9f9af9f72f89a87
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/e8db6cfea7ea/disk-3dea0e7f.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/eeb133c8268e/vmlinux-3dea0e7f.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/9478525201a1/Image-3dea0e7f.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+4d61e9...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 14538 at mm/page_alloc.c:5449 __alloc_pages+0x2b4/0x470 mm/page_alloc.c:5449
Modules linked in:
CPU: 0 PID: 14538 Comm: syz.3.2407 Not tainted 5.15.186-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __alloc_pages+0x2b4/0x470 mm/page_alloc.c:5449
lr : __alloc_pages+0xac/0x470 mm/page_alloc.c:5442
sp : ffff800021507700
x29: ffff8000215077d0 x28: 1ffff000035c6cc8 x27: ffff800021507720
x26: ffff80001ae36640 x25: dfff800000000000 x24: ffff7000042a0ee4
x23: ffff80001ae36644 x22: 0000000000000000 x21: 0000000000040dc0
x20: 0000000000000000 x19: 0000000000000019 x18: 0000000000000000
x17: 0000000000000000 x16: ffff800008822af4 x15: 0000000000000005
x14: 0000000000ff0100 x13: ffffffffffffffff x12: 0000000000000005
x11: 1ffff000042a0ee8 x10: 0000000000000000 x9 : 0000000000000000
x8 : ffff800021507768 x7 : 0000000000000000 x6 : ffff800021507c40
x5 : ffff800021507c40 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000008 x1 : 0000000000000000 x0 : ffff800021507740
Call trace:
__alloc_pages+0x2b4/0x470 mm/page_alloc.c:5449
alloc_pages+0x34c/0x5c0 mm/mempolicy.c:-1
kmalloc_order+0x40/0x160 mm/slab_common.c:986
kmalloc_order_trace+0x30/0x244 mm/slab_common.c:1002
kmalloc_large include/linux/slab.h:533 [inline]
__kmalloc+0x318/0x44c mm/slub.c:4396
kmalloc_array include/linux/slab.h:644 [inline]
kcalloc include/linux/slab.h:673 [inline]
comedi_unlocked_ioctl+0x914/0xdcc drivers/comedi/comedi_fops.c:2237
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+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 518
hardirqs last enabled at (517): [<ffff80000884efa0>] kasan_quarantine_put+0xc4/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (518): [<ffff8000111cabbc>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (260): [<ffff800008031f40>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (258): [<ffff800008031f0c>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace 432199f2d1802a63 ]---
---
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