BUG: spinlock bad magic in bpf_lru_pop_free

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 57f780f1c433 atlantic: Fix driver resume flow.
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=1045b31b300000
kernel config: https://syzkaller.appspot.com/x/.config?x=765eea9a273a8879
dashboard link: https://syzkaller.appspot.com/bug?extid=9e56d539ab08fff1ac06
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
CC: [and...@kernel.org a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net john.fa...@gmail.com ka...@fb.com kps...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org songliu...@fb.com y...@fb.com 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+9e56d5...@syzkaller.appspotmail.com

BUG: spinlock bad magic on CPU#1, syz-executor.0/29788
lock: 0xffffe8ffffd74468, .magic: 00000000, .owner: <none>/-1, .owner_cpu: -1
CPU: 1 PID: 29788 Comm: syz-executor.0 Not tainted 5.14.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:105
debug_spin_lock_before kernel/locking/spinlock_debug.c:83 [inline]
do_raw_spin_lock+0x216/0x2b0 kernel/locking/spinlock_debug.c:112
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:117 [inline]
_raw_spin_lock_irqsave+0x41/0x50 kernel/locking/spinlock.c:159
bpf_common_lru_pop_free kernel/bpf/bpf_lru_list.c:443 [inline]
bpf_lru_pop_free+0x30c/0x16d0 kernel/bpf/bpf_lru_list.c:499
prealloc_lru_pop+0x26/0x90 kernel/bpf/hashtab.c:264
htab_lru_map_update_elem+0x157/0x7b0 kernel/bpf/hashtab.c:1102
bpf_map_update_value.isra.0+0x6a7/0x8e0 kernel/bpf/syscall.c:206
generic_map_update_batch+0x3cf/0x560 kernel/bpf/syscall.c:1371
bpf_map_do_batch+0x3d5/0x510 kernel/bpf/syscall.c:4076
__sys_bpf+0x1d66/0x53b0 kernel/bpf/syscall.c:4533
__do_sys_bpf kernel/bpf/syscall.c:4573 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4571 [inline]
__x64_sys_bpf+0x75/0xb0 kernel/bpf/syscall.c:4571
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x4665f9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5f3bdbc188 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 000000000056bf80 RCX: 00000000004665f9
RDX: 0000000000000038 RSI: 0000000020000580 RDI: 000000000000001a
RBP: 00000000004bfcc4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf80
R13: 00007ffe8f3bb10f R14: 00007f5f3bdbc300 R15: 0000000000022000


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