INFO: trying to register non-static key in try_to_wake_up

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a834132b Linux 4.19.140
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=159afb36900000
kernel config: https://syzkaller.appspot.com/x/.config?x=cf0941721f5dace0
dashboard link: https://syzkaller.appspot.com/bug?extid=0db9db36c42d36f10e58
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+0db9db...@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: 2637 Comm: syz-executor.5 Not tainted 4.19.140-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
try_to_wake_up+0x7b/0x1050 kernel/sched/core.c:1961
signal_wake_up_state kernel/signal.c:761 [inline]
signal_wake_up include/linux/sched/signal.h:389 [inline]
zap_other_threads+0x1da/0x290 kernel/signal.c:1333
do_group_exit+0x25f/0x310 kernel/exit.c:985
__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:0x45d4d9
Code: 5d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffe1c5bedc8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 000000000000001e RCX: 000000000045d4d9
RDX: 0000000000416e21 RSI: fffffffffffffff7 RDI: 0000000000000000
RBP: 0000000000000000 R08: 000000007b2b36ce R09: 00007ffe1c5bee20
R10: ffffffff812fae43 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe1c5bee20 R14: 0000000000000000 R15: 00007ffe1c5bee30
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.