[v6.1] WARNING in input_mt_init_slots

3 views
Skip to first unread message

syzbot

unread,
Mar 8, 2023, 7:07:50 AM3/8/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1626716cc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=690b9ff41783cd73
dashboard link: https://syzkaller.appspot.com/bug?extid=2df60626c75e6a7751f4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/db869f2ed2bd/disk-42616e0f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/37951bbe5829/vmlinux-42616e0f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23aa1a75ce0f/bzImage-42616e0f.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2df606...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 8510 at mm/page_alloc.c:5534 __alloc_pages+0x421/0x7e0 mm/page_alloc.c:5534
Modules linked in:
CPU: 0 PID: 8510 Comm: syz-executor.4 Not tainted 6.1.15-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:__alloc_pages+0x421/0x7e0 mm/page_alloc.c:5534
Code: fc ff df 0f 85 fa 00 00 00 44 89 e9 81 e1 7f ff ff ff a9 00 00 04 00 41 0f 44 cd 41 89 cd e9 ea 00 00 00 c6 05 74 f4 69 0c 01 <0f> 0b 41 83 fc 0a 0f 86 b4 fc ff ff 45 31 e4 48 c7 44 24 20 0e 36
RSP: 0018:ffffc90003597b00 EFLAGS: 00010246
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc90003597b88
RBP: ffffc90003597c10 R08: dffffc0000000000 R09: ffffc90003597b60
R10: 0000000000000000 R11: dffffc0000000001 R12: 000000000000001a
R13: 0000000000040dc0 R14: 1ffff920006b2f68 R15: 1ffff920006b2f64
FS: 00007f2cf6c24700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31323000 CR3: 0000000077385000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__alloc_pages_node include/linux/gfp.h:237 [inline]
alloc_pages_node include/linux/gfp.h:260 [inline]
__kmalloc_large_node+0x91/0x1d0 mm/slab_common.c:1096
__do_kmalloc_node mm/slab_common.c:943 [inline]
__kmalloc+0xfe/0x1a0 mm/slab_common.c:968
kmalloc include/linux/slab.h:558 [inline]
kzalloc include/linux/slab.h:689 [inline]
input_mt_init_slots+0xc6/0x9c0 drivers/input/input-mt.c:50
uinput_create_device+0x512/0x620 drivers/input/misc/uinput.c:327
uinput_ioctl_handler+0xa83/0x16d0 drivers/input/misc/uinput.c:870
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f2cf5e8c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2cf6c24168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f2cf5fabf80 RCX: 00007f2cf5e8c0f9
RDX: 0000000000000000 RSI: 0000000000005501 RDI: 0000000000000003
RBP: 00007f2cf5ee7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffcd48aecdf R14: 00007f2cf6c24300 R15: 0000000000022000
</TASK>


---
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.

syzbot

unread,
Mar 8, 2023, 8:04:46 AM3/8/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14048e14c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=690b9ff41783cd73
dashboard link: https://syzkaller.appspot.com/bug?extid=2df60626c75e6a7751f4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15fe71f4c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=152e2adac80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/db869f2ed2bd/disk-42616e0f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/37951bbe5829/vmlinux-42616e0f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23aa1a75ce0f/bzImage-42616e0f.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2df606...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 3627 at mm/page_alloc.c:5534 __alloc_pages+0x421/0x7e0 mm/page_alloc.c:5534
Modules linked in:
CPU: 0 PID: 3627 Comm: syz-executor401 Not tainted 6.1.15-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:__alloc_pages+0x421/0x7e0 mm/page_alloc.c:5534
Code: fc ff df 0f 85 fa 00 00 00 44 89 e9 81 e1 7f ff ff ff a9 00 00 04 00 41 0f 44 cd 41 89 cd e9 ea 00 00 00 c6 05 74 f4 69 0c 01 <0f> 0b 41 83 fc 0a 0f 86 b4 fc ff ff 45 31 e4 48 c7 44 24 20 0e 36
RSP: 0018:ffffc90003c1fb00 EFLAGS: 00010246
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc90003c1fb88
RBP: ffffc90003c1fc10 R08: dffffc0000000000 R09: ffffc90003c1fb60
R10: 0000000000000000 R11: dffffc0000000001 R12: 000000000000001a
R13: 0000000000040dc0 R14: 1ffff92000783f68 R15: 1ffff92000783f64
FS: 0000555555898300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055e8f0136da0 CR3: 000000002366b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__alloc_pages_node include/linux/gfp.h:237 [inline]
alloc_pages_node include/linux/gfp.h:260 [inline]
__kmalloc_large_node+0x91/0x1d0 mm/slab_common.c:1096
__do_kmalloc_node mm/slab_common.c:943 [inline]
__kmalloc+0xfe/0x1a0 mm/slab_common.c:968
kmalloc include/linux/slab.h:558 [inline]
kzalloc include/linux/slab.h:689 [inline]
input_mt_init_slots+0xc6/0x9c0 drivers/input/input-mt.c:50
uinput_create_device+0x512/0x620 drivers/input/misc/uinput.c:327
uinput_ioctl_handler+0xa83/0x16d0 drivers/input/misc/uinput.c:870
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6582bc3789
Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc3b698828 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6582bc3789
RDX: 0000000000000000 RSI: 0000000000005501 RDI: 0000000000000003
RBP: 00007f6582b87770 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6582b87800
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>

syzbot

unread,
Mar 8, 2023, 7:28:44 PM3/8/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1699c07cc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b57cfa804330c3b7
dashboard link: https://syzkaller.appspot.com/bug?extid=e5b47a2bbc8db35fdd42
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=165c19f4c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e76beac80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8088989394e3/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2651d6753959/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f3fa3f994f9a/Image-d9b4a0c8.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e5b47a...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 4051 at mm/page_alloc.c:5396 __alloc_pages+0x40c/0x798 mm/page_alloc.c:5396
Modules linked in:
CPU: 1 PID: 4051 Comm: syz-executor428 Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __alloc_pages+0x40c/0x798 mm/page_alloc.c:5396
lr : __alloc_pages+0xc8/0x798 mm/page_alloc.c:5389
sp : ffff80001c8977c0
x29: ffff80001c8978a0 x28: ffff80001c8977e0 x27: dfff800000000000
x26: ffff700003912efc x25: 0000000000000000 x24: ffff80001c897800
x23: ffff800018476544 x22: 0000000000040dc0 x21: ffff80001c897820
x20: 0000000000000000 x19: 000000000000001a x18: 0000000000000000
x17: ff8080000889bb1c x16: 0000000000000000 x15: ffff80000889bb1c
x14: 0000000000000005 x13: ffffffffffffffff x12: 0000000000000005
x11: 1ffff00003912f04 x10: 0000000000000000 x9 : 0000000000000000
x8 : ffff80001c897848 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000008 x1 : 0000000000000000 x0 : ffff80001c897820
Call trace:
__alloc_pages+0x40c/0x798 mm/page_alloc.c:5396
alloc_pages+0x390/0x634
kmalloc_order+0x40/0x154 mm/slab_common.c:966
kmalloc_order_trace+0x30/0x284 mm/slab_common.c:982
kmalloc_large include/linux/slab.h:520 [inline]
__kmalloc+0x32c/0x404 mm/slub.c:4396
kmalloc include/linux/slab.h:596 [inline]
kzalloc include/linux/slab.h:721 [inline]
input_mt_init_slots+0xc0/0x818 drivers/input/input-mt.c:49
uinput_create_device+0x3d0/0x528 drivers/input/misc/uinput.c:327
uinput_ioctl_handler+0x700/0x14b0 drivers/input/misc/uinput.c:870
uinput_ioctl+0x38/0x4c drivers/input/misc/uinput.c:1041
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 <unknown>:584
irq event stamp: 13606
hardirqs last enabled at (13605): [<ffff8000088c98f4>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (13606): [<ffff800011976650>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (13314): [<ffff800008020e1c>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (13314): [<ffff800008020e1c>] __do_softirq+0xcac/0xf48 kernel/softirq.c:587
softirqs last disabled at (13305): [<ffff8000081b8624>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (13305): [<ffff8000081b8624>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (13305): [<ffff8000081b8624>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
---[ end trace 453dd4f3d7ce0451 ]---


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
Reply all
Reply to author
Forward
0 new messages