INFO: trying to register non-static key in call_usermodehelper_exec_async

已查看 5 次
跳至第一个未读帖子

syzbot

未读,
2020年8月5日 05:57:242020/8/5
收件人 syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ca4f2c56 Linux 4.14.192
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1697d5cc900000
kernel config: https://syzkaller.appspot.com/x/.config?x=60834b36c72d3e64
dashboard link: https://syzkaller.appspot.com/bug?extid=4f02d01e82664f1483c8
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+4f02d0...@syzkaller.appspotmail.com

INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 5573 Comm: kworker/u4:12 Not tainted 4.14.192-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
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_irq include/linux/spinlock_api_smp.h:128 [inline]
_raw_spin_lock_irq+0x5b/0x80 kernel/locking/spinlock.c:168
spin_lock_irq include/linux/spinlock.h:342 [inline]
call_usermodehelper_exec_async+0x57/0x4a0 kernel/umh.c:69
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
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:
CPU: 1 PID: 5573 Comm: kworker/u4:12 Not tainted 4.14.192-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88820750a300 task.stack: ffff88821adb0000
RIP: 0010:__wake_up_common+0x9e/0x5d0 kernel/sched/wait.c:90
RSP: 0018:ffff88821adb7c40 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff888000133540 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000003 RDI: 0000000000000000
RBP: 0000000000000003 R08: ffffffffffffffe8 R09: ffff88821adb7ce0
R10: 0000000000000000 R11: ffff88820750a300 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000004010
FS: 0000000000000000(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3242a000 CR3: 0000000069021000 CR4: 00000000001426e0
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
signalfd_cleanup+0x5b/0x70 fs/signalfd.c:48
__cleanup_sighand kernel/fork.c:1363 [inline]
__cleanup_sighand+0x22/0x40 kernel/fork.c:1360
__exit_signal kernel/exit.c:166 [inline]
release_task+0xb30/0x1380 kernel/exit.c:200
exit_notify kernel/exit.c:740 [inline]
do_exit+0x131d/0x27f0 kernel/exit.c:885
call_usermodehelper_exec_async+0x412/0x4a0 kernel/umh.c:113
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
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
RIP: __wake_up_common+0x9e/0x5d0 kernel/sched/wait.c:90 RSP: ffff88821adb7c40
---[ end trace 61e798ef5edb87fa ]---


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

未读,
2020年12月3日 04:57:142020/12/3
收件人 syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
回复全部
回复作者
转发
0 个新帖子