WARNING: locking bug in process_one_work (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ff2e6efd kbuild: Quote OBJCOPY var to avoid a pahole call ..
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=1761cb5fd00000
kernel config: https://syzkaller.appspot.com/x/.config?x=770708ea7cfd4916
dashboard link: https://syzkaller.appspot.com/bug?extid=0a79aa1da1f7c1ce176a
CC: [boqun...@gmail.com linux-...@vger.kernel.org lon...@redhat.com mi...@redhat.com pet...@infradead.org wi...@kernel.org net...@vger.kernel.org]

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+0a79aa...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 3465 at kernel/locking/lockdep.c:895 look_up_lock_class kernel/locking/lockdep.c:895 [inline]
WARNING: CPU: 1 PID: 3465 at kernel/locking/lockdep.c:895 register_lock_class+0x1fb/0x1180 kernel/locking/lockdep.c:1244
Modules linked in:
CPU: 1 PID: 3465 Comm: kworker/1:4 Not tainted 5.13.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: wg-crypt-wg2 wg_packet_decrypt_worker
RIP: 0010:look_up_lock_class kernel/locking/lockdep.c:895 [inline]
RIP: 0010:register_lock_class+0x1fb/0x1180 kernel/locking/lockdep.c:1244
Code: 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 98 0c 00 00 4d 3b 67 18 74 0b 49 81 3f c0 a3 42 8f 74 02 <0f> 0b 85 ed 0f 84 20 01 00 00 f6 44 24 04 01 0f 85 15 01 00 00 83
RSP: 0018:ffffc900016cfa20 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 1ffff920002d9f4b RCX: ffffffff90774720
RDX: 1ffff920002d9fb8 RSI: 0000000000000000 RDI: ffffc900016cfdc0
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff89ede1e0
R13: ffffffff90a623c0 R14: ffffffff9027dd80 R15: ffffc900016cfda8
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000001b0b708 CR3: 0000000021692000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
__lock_acquire+0x102/0x5230 kernel/locking/lockdep.c:4781
lock_acquire kernel/locking/lockdep.c:5512 [inline]
lock_acquire+0x1ab/0x740 kernel/locking/lockdep.c:5477
process_one_work+0x8fc/0x1600 kernel/workqueue.c:2252
worker_thread+0x64c/0x1120 kernel/workqueue.c:2422
kthread+0x3b1/0x4a0 kernel/kthread.c:313
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294


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