INFO: trying to register non-static key in uhid_char_release
13 views
Skip to first unread message
syzbot
Aug 7, 2020, 1:29:17 AM8/7/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: c076c79e Linux 4.19.137
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ac8e34900000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8bacc01843402f4
dashboard link: https://syzkaller.appspot.com/bug?extid=39e8e12e01e60e6cf087
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+39e8e1...@syzkaller.appspotmail.com
hid-generic 0000:0000:0000.0071: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.0072: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 500 Comm: syz-executor.1 Not tainted 4.19.137-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
assign_lock_key kernel/locking/lockdep.c:727 [inline]
register_lock_class+0xe76/0x11c0 kernel/locking/lockdep.c:753
__lock_acquire+0x17d/0x3ff0 kernel/locking/lockdep.c:3303
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:152
__wake_up_common_lock+0xb0/0x170 kernel/sched/wait.c:120
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x9b/0x190 drivers/hid/uhid.c:645
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4167f1
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48 83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffdb1dd8c30 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00000000004167f1
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000792070 R09: 0000000000000000
R10: 00007ffdb1dd8d10 R11: 0000000000000293 R12: 0000000000792078
R13: 0000000000000000 R14: ffffffffffffffff R15: 000000000078bf0c
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 500 Comm: syz-executor.1 Not tainted 4.19.137-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__wake_up_common+0xdf/0x650 kernel/sched/wait.c:85
Code: 05 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 3b 3c 24 0f 84 6a 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 <80> 3c 01 00 0f 85 3e 05 00 00 49 8b 40 18 89 54 24 10 31 db 48 bd
RSP: 0018:ffff88802cdf7cc8 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff88802d94a508 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 1ffffffff1238d04 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffffffffffe8 R09: ffff88802cdf7d68
R10: ffff88802d94a50b R11: ffffffff8ad3605b R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000002c15940(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f41efc8c50 CR3: 00000000a440b000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__wake_up_common_lock+0xcd/0x170 kernel/sched/wait.c:121
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x9b/0x190 drivers/hid/uhid.c:645
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4167f1
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48 83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffdb1dd8c30 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00000000004167f1
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000792070 R09: 0000000000000000
R10: 00007ffdb1dd8d10 R11: 0000000000000293 R12: 0000000000792078
R13: 0000000000000000 R14: ffffffffffffffff R15: 000000000078bf0c
Modules linked in:
---[ end trace 5e54f1b7f7a89a74 ]---
RIP: 0010:__wake_up_common+0xdf/0x650 kernel/sched/wait.c:85
Code: 05 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 3b 3c 24 0f 84 6a 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 <80> 3c 01 00 0f 85 3e 05 00 00 49 8b 40 18 89 54 24 10 31 db 48 bd
RSP: 0018:ffff88802cdf7cc8 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff88802d94a508 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 1ffffffff1238d04 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffffffffffe8 R09: ffff88802cdf7d68
R10: ffff88802d94a50b R11: ffffffff8ad3605b R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000002c15940(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f41efc8c50 CR3: 00000000a440b000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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 found the following issue on:
HEAD commit: c076c79e Linux 4.19.137
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ac8e34900000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8bacc01843402f4
dashboard link: https://syzkaller.appspot.com/bug?extid=39e8e12e01e60e6cf087
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+39e8e1...@syzkaller.appspotmail.com
hid-generic 0000:0000:0000.0071: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.0072: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 500 Comm: syz-executor.1 Not tainted 4.19.137-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
assign_lock_key kernel/locking/lockdep.c:727 [inline]
register_lock_class+0xe76/0x11c0 kernel/locking/lockdep.c:753
__lock_acquire+0x17d/0x3ff0 kernel/locking/lockdep.c:3303
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:152
__wake_up_common_lock+0xb0/0x170 kernel/sched/wait.c:120
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x9b/0x190 drivers/hid/uhid.c:645
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4167f1
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48 83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffdb1dd8c30 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00000000004167f1
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000792070 R09: 0000000000000000
R10: 00007ffdb1dd8d10 R11: 0000000000000293 R12: 0000000000792078
R13: 0000000000000000 R14: ffffffffffffffff R15: 000000000078bf0c
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 500 Comm: syz-executor.1 Not tainted 4.19.137-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__wake_up_common+0xdf/0x650 kernel/sched/wait.c:85
Code: 05 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 3b 3c 24 0f 84 6a 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 <80> 3c 01 00 0f 85 3e 05 00 00 49 8b 40 18 89 54 24 10 31 db 48 bd
RSP: 0018:ffff88802cdf7cc8 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff88802d94a508 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 1ffffffff1238d04 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffffffffffe8 R09: ffff88802cdf7d68
R10: ffff88802d94a50b R11: ffffffff8ad3605b R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000002c15940(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f41efc8c50 CR3: 00000000a440b000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__wake_up_common_lock+0xcd/0x170 kernel/sched/wait.c:121
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x9b/0x190 drivers/hid/uhid.c:645
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4167f1
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48 83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffdb1dd8c30 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00000000004167f1
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000792070 R09: 0000000000000000
R10: 00007ffdb1dd8d10 R11: 0000000000000293 R12: 0000000000792078
R13: 0000000000000000 R14: ffffffffffffffff R15: 000000000078bf0c
Modules linked in:
---[ end trace 5e54f1b7f7a89a74 ]---
RIP: 0010:__wake_up_common+0xdf/0x650 kernel/sched/wait.c:85
Code: 05 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 3b 3c 24 0f 84 6a 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 <80> 3c 01 00 0f 85 3e 05 00 00 49 8b 40 18 89 54 24 10 31 db 48 bd
RSP: 0018:ffff88802cdf7cc8 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff88802d94a508 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 1ffffffff1238d04 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffffffffffe8 R09: ffff88802cdf7d68
R10: ffff88802d94a50b R11: ffffffff8ad3605b R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000002c15940(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f41efc8c50 CR3: 00000000a440b000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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
Aug 7, 2020, 2:08:23 AM8/7/20
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: c076c79e Linux 4.19.137
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1763e7ec900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=137c63c6900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+39e8e1...@syzkaller.appspotmail.com
hid-generic 0000:0000:0000.0004: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.0005: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.0006: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.0007: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
do_exit+0xbb2/0x2b70 kernel/exit.c:887
do_group_exit+0x125/0x310 kernel/exit.c:990
__do_sys_exit_group kernel/exit.c:1001 [inline]
__se_sys_exit_group kernel/exit.c:999 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:999
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x43ff68
Code: Bad RIP value.
RSP: 002b:00007ffc0e8aa438 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043ff68
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004bfb90 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d2180 R14: 0000000000000000 R15: 0000000000000000
RAX: dffffc0000000000 RBX: ffff888089721e08 RCX: 0000000000000000
R10: ffff888089721e0b R11: ffffffff8ad3601b R12: 0000000000000001
do_exit+0xbb2/0x2b70 kernel/exit.c:887
do_group_exit+0x125/0x310 kernel/exit.c:990
__do_sys_exit_group kernel/exit.c:1001 [inline]
__se_sys_exit_group kernel/exit.c:999 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:999
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x43ff68
Code: Bad RIP value.
RSP: 002b:00007ffc0e8aa438 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043ff68
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004bfb90 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d2180 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace d9497fefcdbd6b5f ]---
RAX: dffffc0000000000 RBX: ffff888089721e08 RCX: 0000000000000000
R10: ffff888089721e0b R11: ffffffff8ad3601b R12: 0000000000000001
HEAD commit: c076c79e Linux 4.19.137
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=b8bacc01843402f4
dashboard link: https://syzkaller.appspot.com/bug?extid=39e8e12e01e60e6cf087
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15ba83c6900000
dashboard link: https://syzkaller.appspot.com/bug?extid=39e8e12e01e60e6cf087
compiler: gcc (GCC) 10.1.0-syz 20200507
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=137c63c6900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+39e8e1...@syzkaller.appspotmail.com
hid-generic 0000:0000:0000.0005: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.0006: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.0007: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 0 PID: 6550 Comm: syz-executor986 Not tainted 4.19.137-syzkaller #0
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
assign_lock_key kernel/locking/lockdep.c:727 [inline]
register_lock_class+0xe76/0x11c0 kernel/locking/lockdep.c:753
__lock_acquire+0x17d/0x3ff0 kernel/locking/lockdep.c:3303
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:152
__wake_up_common_lock+0xb0/0x170 kernel/sched/wait.c:120
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x9b/0x190 drivers/hid/uhid.c:645
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
assign_lock_key kernel/locking/lockdep.c:727 [inline]
register_lock_class+0xe76/0x11c0 kernel/locking/lockdep.c:753
__lock_acquire+0x17d/0x3ff0 kernel/locking/lockdep.c:3303
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:152
__wake_up_common_lock+0xb0/0x170 kernel/sched/wait.c:120
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x9b/0x190 drivers/hid/uhid.c:645
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
do_exit+0xbb2/0x2b70 kernel/exit.c:887
do_group_exit+0x125/0x310 kernel/exit.c:990
__do_sys_exit_group kernel/exit.c:1001 [inline]
__se_sys_exit_group kernel/exit.c:999 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:999
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x43ff68
Code: Bad RIP value.
RSP: 002b:00007ffc0e8aa438 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043ff68
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004bfb90 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d2180 R14: 0000000000000000 R15: 0000000000000000
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 6550 Comm: syz-executor986 Not tainted 4.19.137-syzkaller #0
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__wake_up_common+0xdf/0x650 kernel/sched/wait.c:85
Code: 05 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 3b 3c 24 0f 84 6a 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 <80> 3c 01 00 0f 85 3e 05 00 00 49 8b 40 18 89 54 24 10 31 db 48 bd
RSP: 0018:ffff8880a6ab7b88 EFLAGS: 00010046
RIP: 0010:__wake_up_common+0xdf/0x650 kernel/sched/wait.c:85
Code: 05 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 3b 3c 24 0f 84 6a 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 <80> 3c 01 00 0f 85 3e 05 00 00 49 8b 40 18 89 54 24 10 31 db 48 bd
RAX: dffffc0000000000 RBX: ffff888089721e08 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 1ffffffff1238d04 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffffffffffe8 R09: ffff8880a6ab7c28
R10: ffff888089721e0b R11: ffffffff8ad3601b R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000043ff3e CR3: 0000000008c6d000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__wake_up_common_lock+0xcd/0x170 kernel/sched/wait.c:121
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x9b/0x190 drivers/hid/uhid.c:645
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__wake_up_common_lock+0xcd/0x170 kernel/sched/wait.c:121
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x9b/0x190 drivers/hid/uhid.c:645
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
do_exit+0xbb2/0x2b70 kernel/exit.c:887
do_group_exit+0x125/0x310 kernel/exit.c:990
__do_sys_exit_group kernel/exit.c:1001 [inline]
__se_sys_exit_group kernel/exit.c:999 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:999
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x43ff68
Code: Bad RIP value.
RSP: 002b:00007ffc0e8aa438 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043ff68
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004bfb90 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d2180 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace d9497fefcdbd6b5f ]---
RIP: 0010:__wake_up_common+0xdf/0x650 kernel/sched/wait.c:85
Code: 05 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 3b 3c 24 0f 84 6a 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 <80> 3c 01 00 0f 85 3e 05 00 00 49 8b 40 18 89 54 24 10 31 db 48 bd
RSP: 0018:ffff8880a6ab7b88 EFLAGS: 00010046
Code: 05 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 3b 3c 24 0f 84 6a 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 <80> 3c 01 00 0f 85 3e 05 00 00 49 8b 40 18 89 54 24 10 31 db 48 bd
RAX: dffffc0000000000 RBX: ffff888089721e08 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 1ffffffff1238d04 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffffffffffe8 R09: ffff8880a6ab7c28
R10: ffff888089721e0b R11: ffffffff8ad3601b R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000043ff3e CR3: 0000000008c6d000 CR4: 00000000001406f0
syzbot
Aug 10, 2020, 7:36:26 AM8/10/20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 14b58326 Linux 4.14.193
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=119ceb62900000
kernel config: https://syzkaller.appspot.com/x/.config?x=68ef0287ccbc3b42
dashboard link: https://syzkaller.appspot.com/bug?extid=a01edcf7e7543c247fe4
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d70026900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a01edc...@syzkaller.appspotmail.com
hid-generic 0000:0000:0000.002A: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.002B: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.002C: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
register_lock_class+0x32b/0x1320 kernel/locking/lockdep.c:768
__lock_acquire+0x167/0x3f20 kernel/locking/lockdep.c:3378
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
__wake_up_common_lock+0x9d/0x140 kernel/sched/wait.c:124
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x90/0x180 drivers/hid/uhid.c:645
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa08/0x27f0 kernel/exit.c:865
do_group_exit+0x100/0x2e0 kernel/exit.c:962
SYSC_exit_group kernel/exit.c:973 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:971
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x43ff68
RSP: 002b:00007fff5c569db8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
CPU: 0 PID: 6677 Comm: syz-executor452 Not tainted 4.14.193-syzkaller #0
RIP: 0010:__wake_up_common+0x9e/0x5d0 kernel/sched/wait.c:90
RSP: 0018:ffff88808c95fba0 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff888092fa3108 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffffffffffe8 R09: ffff88808c95fc40
R10: 0000000000000001 R11: ffff8880921120c0 R12: 0000000000000001
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x90/0x180 drivers/hid/uhid.c:645
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa08/0x27f0 kernel/exit.c:865
do_group_exit+0x100/0x2e0 kernel/exit.c:962
SYSC_exit_group kernel/exit.c:973 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:971
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x43ff68
RSP: 002b:00007fff5c569db8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RIP: __wake_up_common+0x9e/0x5d0 kernel/sched/wait.c:90 RSP: ffff88808c95fba0
---[ end trace 07e61a80e3a98797 ]---
---
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
syzbot found the following issue on:
HEAD commit: 14b58326 Linux 4.14.193
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=119ceb62900000
kernel config: https://syzkaller.appspot.com/x/.config?x=68ef0287ccbc3b42
dashboard link: https://syzkaller.appspot.com/bug?extid=a01edcf7e7543c247fe4
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1518583c900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d70026900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
hid-generic 0000:0000:0000.002A: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.002B: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
hid-generic 0000:0000:0000.002C: hidraw0: <UNKNOWN> HID v0.00 Device [syz1] on 1
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 0 PID: 6677 Comm: syz-executor452 Not tainted 4.14.193-syzkaller #0
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
Call Trace:
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
register_lock_class+0x32b/0x1320 kernel/locking/lockdep.c:768
__lock_acquire+0x167/0x3f20 kernel/locking/lockdep.c:3378
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:160
__wake_up_common_lock+0x9d/0x140 kernel/sched/wait.c:124
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x90/0x180 drivers/hid/uhid.c:645
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa08/0x27f0 kernel/exit.c:865
do_group_exit+0x100/0x2e0 kernel/exit.c:962
SYSC_exit_group kernel/exit.c:973 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:971
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x43ff68
RSP: 002b:00007fff5c569db8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043ff68
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004bfb90 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d2180 R14: 0000000000000000 R15: 0000000000000000
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004bfb90 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d2180 R14: 0000000000000000 R15: 0000000000000000
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 6677 Comm: syz-executor452 Not tainted 4.14.193-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880921120c0 task.stack: ffff88808c958000
RIP: 0010:__wake_up_common+0x9e/0x5d0 kernel/sched/wait.c:90
RSP: 0018:ffff88808c95fba0 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff888092fa3108 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffffffffffe8 R09: ffff88808c95fc40
R10: 0000000000000001 R11: ffff8880921120c0 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880aea00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000004bfbc8 CR3: 0000000007c6a000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__wake_up_common_lock+0xba/0x140 kernel/sched/wait.c:125
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
uhid_dev_destroy drivers/hid/uhid.c:566 [inline]
uhid_char_release+0x90/0x180 drivers/hid/uhid.c:645
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa08/0x27f0 kernel/exit.c:865
do_group_exit+0x100/0x2e0 kernel/exit.c:962
SYSC_exit_group kernel/exit.c:973 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:971
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x43ff68
RSP: 002b:00007fff5c569db8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043ff68
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004bfb90 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d2180 R14: 0000000000000000 R15: 0000000000000000
Code: bf 04 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 3b 3c 24 0f 84 6a 02 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 f9 48 c1 e9 03 <80> 3c 01 00 0f 85 a4 04 00 00 49 8b 40 18 89 54 24 10 31 db 48
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004bfb90 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 00000000004002c8 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d2180 R14: 0000000000000000 R15: 0000000000000000
RIP: __wake_up_common+0x9e/0x5d0 kernel/sched/wait.c:90 RSP: ffff88808c95fba0
---[ end trace 07e61a80e3a98797 ]---
---
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.
https://goo.gl/tpsmEJ#testing-patches
syzbot
Sep 28, 2020, 2:01:06 PM9/28/20
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit abae259fdccc5e41ff302dd80a2b944ce385c970
Author: Marc Zyngier <m...@kernel.org>
Date: Sat Aug 29 11:26:01 2020 +0000
HID: core: Correctly handle ReportSize being zero
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17bf1b3d900000
start commit: f6d5cb9e Linux 4.19.142
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=30067df04d3254aa
dashboard link: https://syzkaller.appspot.com/bug?extid=39e8e12e01e60e6cf087
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101be056900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16cbb561900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: HID: core: Correctly handle ReportSize being zero
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
commit abae259fdccc5e41ff302dd80a2b944ce385c970
Author: Marc Zyngier <m...@kernel.org>
Date: Sat Aug 29 11:26:01 2020 +0000
HID: core: Correctly handle ReportSize being zero
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17bf1b3d900000
start commit: f6d5cb9e Linux 4.19.142
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=30067df04d3254aa
dashboard link: https://syzkaller.appspot.com/bug?extid=39e8e12e01e60e6cf087
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101be056900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16cbb561900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: HID: core: Correctly handle ReportSize being zero
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot
Sep 28, 2020, 5:48:09 PM9/28/20
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:
commit 9e5894b7e2229e6d89319864fb08304571fd44f7
Author: Marc Zyngier <m...@kernel.org>
Date: Sat Aug 29 11:26:01 2020 +0000
HID: core: Correctly handle ReportSize being zero
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=117525e3900000
Date: Sat Aug 29 11:26:01 2020 +0000
HID: core: Correctly handle ReportSize being zero
start commit: d7e78d08 Linux 4.14.195
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=6608b656f49b4e8c
dashboard link: https://syzkaller.appspot.com/bug?extid=a01edcf7e7543c247fe4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=163be056900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149400c9900000
Reply all
Reply to author
Forward
0 new messages