INFO: trying to register non-static key in do_send_sig_info

5 views
Skip to first unread message

syzbot

unread,
Jun 1, 2020, 11:13:18 PM6/1/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 4f68020f Linux 4.14.182
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17e222f2100000
kernel config: https://syzkaller.appspot.com/x/.config?x=512ec6eb8f94d0c8
dashboard link: https://syzkaller.appspot.com/bug?extid=89333d2445f4c5a4af7a
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

overlayfs: failed to resolve './file1': -2
overlayfs: failed to resolve './file1': -2
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 3644 Comm: systemd-udevd Not tainted 4.14.182-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+0x180/0x42a0 kernel/locking/lockdep.c:3378
lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:152
spin_lock include/linux/spinlock.h:317 [inline]
__lock_task_sighand+0x152/0x670 kernel/signal.c:1319
lock_task_sighand include/linux/sched/signal.h:598 [inline]
do_send_sig_info+0x6a/0x100 kernel/signal.c:1217
group_send_sig_info+0xe6/0x170 kernel/signal.c:1344
kill_pid_info+0x97/0x180 kernel/signal.c:1378
kill_something_info kernel/signal.c:1461 [inline]
SYSC_kill kernel/signal.c:3052 [inline]
SyS_kill+0x3f4/0x560 kernel/signal.c:3042
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f796bc8b317
RSP: 002b:00007ffc7b94f0a8 EFLAGS: 00000297 ORIG_RAX: 000000000000003e
RAX: ffffffffffffffda RBX: 000055e407941a60 RCX: 00007f796bc8b317
RDX: 000055e4079f1ab0 RSI: 000000000000000f RDI: 00000000000065d3
RBP: 00007ffc7b94f0c0 R08: 0000000000000000 R09: 000055e407a0e3e0
R10: 000000000000000f R11: 0000000000000297 R12: 00007ffc7b94f0b8
R13: 000055e407a05740 R14: 000055e407a05720 R15: 0000000000000001
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: 3644 Comm: systemd-udevd Not tainted 4.14.182-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88808e90a140 task.stack: ffff88808e910000
RIP: 0010:__wake_up_common+0x9e/0x5d0 kernel/sched/wait.c:90
RSP: 0018:ffff88808e917b78 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff88800017d300 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000003 RDI: 0000000000000000
RBP: 0000000000000003 R08: ffffffffffffffe8 R09: ffff88808e917c18
R10: ffffed1013ee97ac R11: ffff88808e90a140 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 00007f796cec08c0(0000) GS:ffff8880aed00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f796cca9028 CR3: 000000008fbbd000 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_notify include/linux/signalfd.h:22 [inline]
__send_signal+0x104a/0x1280 kernel/signal.c:1145
do_send_sig_info+0x86/0x100 kernel/signal.c:1218
group_send_sig_info+0xe6/0x170 kernel/signal.c:1344
kill_pid_info+0x97/0x180 kernel/signal.c:1378
kill_something_info kernel/signal.c:1461 [inline]
SYSC_kill kernel/signal.c:3052 [inline]
SyS_kill+0x3f4/0x560 kernel/signal.c:3042
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f796bc8b317
RSP: 002b:00007ffc7b94f0a8 EFLAGS: 00000297 ORIG_RAX: 000000000000003e
RAX: ffffffffffffffda RBX: 000055e407941a60 RCX: 00007f796bc8b317
RDX: 000055e4079f1ab0 RSI: 000000000000000f RDI: 00000000000065d3
RBP: 00007ffc7b94f0c0 R08: 0000000000000000 R09: 000055e407a0e3e0
R10: 000000000000000f R11: 0000000000000297 R12: 00007ffc7b94f0b8
R13: 000055e407a05740 R14: 000055e407a05720 R15: 0000000000000001
Code: bc 04 00 00 4c 8b 43 38 49 83 e8 18 49 8d 78 18 48 39 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 a1 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: ffff88808e917b78
---[ end trace 65b6f86b7b98026a ]---


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Sep 29, 2020, 11:13:20 PM9/29/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages