[v5.15] inconsistent lock state in htab_lru_map_delete_elem

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=171f38c2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=aa7cc5af17a66f4e3e63
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1066d512580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14efa192580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed7568bc5bb4/disk-cc5ec876.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e343e0aaac77/vmlinux-cc5ec876.xz
kernel image: https://storage.googleapis.com/syzbot-assets/089870f2a980/bzImage-cc5ec876.xz

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

================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {INITIAL USE} -> {IN-NMI} usage.
syz.0.411/4904 [HC1[1]:SC0[0]:HE0:SE1] takes:
ffff88802b644068 (&htab->lockdep_key#395){....}-{2:2}, at: htab_lock_bucket kernel/bpf/hashtab.c:183 [inline]
ffff88802b644068 (&htab->lockdep_key#395){....}-{2:2}, at: htab_lru_map_delete_elem+0x1b1/0x640 kernel/bpf/hashtab.c:1397
{INITIAL USE} state was registered at:
lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xa4/0xf0 kernel/locking/spinlock.c:162
htab_lock_bucket kernel/bpf/hashtab.c:183 [inline]
htab_lru_map_delete_elem+0x1b1/0x640 kernel/bpf/hashtab.c:1397
bpf_prog_2c29ac5cdc6b1842+0x3a/0xc08
bpf_dispatcher_nop_func include/linux/bpf.h:888 [inline]
__bpf_prog_run include/linux/filter.h:628 [inline]
bpf_prog_run include/linux/filter.h:635 [inline]
bpf_overflow_handler+0x1c4/0x4c0 kernel/events/core.c:10297
__perf_event_overflow+0x364/0x530 kernel/events/core.c:9515
perf_swevent_overflow kernel/events/core.c:9591 [inline]
perf_swevent_event+0x4ad/0x530 kernel/events/core.c:9629
perf_bp_event+0x224/0x290 kernel/events/core.c:10484
hw_breakpoint_handler arch/x86/kernel/hw_breakpoint.c:555 [inline]
hw_breakpoint_exceptions_notify+0x152/0x470 arch/x86/kernel/hw_breakpoint.c:586
notifier_call_chain kernel/notifier.c:83 [inline]
atomic_notifier_call_chain+0x15d/0x280 kernel/notifier.c:198
notify_die+0x12d/0x180 kernel/notifier.c:529
notify_debug+0x20/0x30 arch/x86/kernel/traps.c:872
exc_debug_user arch/x86/kernel/traps.c:998 [inline]
noist_exc_debug+0x73/0x120 arch/x86/kernel/traps.c:1035
asm_exc_debug+0x2f/0x40 arch/x86/include/asm/idtentry.h:642
irq event stamp: 1928
hardirqs last enabled at (1927): [<ffffffff89a949f6>] exc_debug_kernel arch/x86/kernel/traps.c:947 [inline]
hardirqs last enabled at (1927): [<ffffffff89a949f6>] exc_debug+0xe6/0x130 arch/x86/kernel/traps.c:1029
hardirqs last disabled at (1928): [<ffffffff89a9497e>] exc_debug_kernel arch/x86/kernel/traps.c:893 [inline]
hardirqs last disabled at (1928): [<ffffffff89a9497e>] exc_debug+0x6e/0x130 arch/x86/kernel/traps.c:1029
softirqs last enabled at (1654): [<ffffffff81856560>] bpf_prog_load+0x1150/0x1550 kernel/bpf/syscall.c:2380
softirqs last disabled at (1652): [<ffffffff8183c969>] spin_lock_bh include/linux/spinlock.h:369 [inline]
softirqs last disabled at (1652): [<ffffffff8183c969>] bpf_ksym_add+0x29/0x340 kernel/bpf/core.c:633

other info that might help us debug this:
Possible unsafe locking scenario:

CPU0
----
lock(&htab->lockdep_key#395);
<Interrupt>
lock(&htab->lockdep_key#395);

*** DEADLOCK ***

no locks held by syz.0.411/4904.

stack backtrace:
CPU: 1 PID: 4904 Comm: syz.0.411 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<#DB>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
lock_acquire+0x2b2/0x3f0 kernel/locking/lockdep.c:5614
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xa4/0xf0 kernel/locking/spinlock.c:162
htab_lock_bucket kernel/bpf/hashtab.c:183 [inline]
htab_lru_map_delete_elem+0x1b1/0x640 kernel/bpf/hashtab.c:1397
bpf_prog_2c29ac5cdc6b1842+0x3a/0xc08
bpf_dispatcher_nop_func include/linux/bpf.h:888 [inline]
__bpf_prog_run include/linux/filter.h:628 [inline]
bpf_prog_run include/linux/filter.h:635 [inline]
bpf_overflow_handler+0x1c4/0x4c0 kernel/events/core.c:10297
__perf_event_overflow+0x364/0x530 kernel/events/core.c:9515
perf_swevent_overflow kernel/events/core.c:9591 [inline]
perf_swevent_event+0x4ad/0x530 kernel/events/core.c:9629
perf_bp_event+0x224/0x290 kernel/events/core.c:10484
hw_breakpoint_handler arch/x86/kernel/hw_breakpoint.c:555 [inline]
hw_breakpoint_exceptions_notify+0x152/0x470 arch/x86/kernel/hw_breakpoint.c:586
notifier_call_chain kernel/notifier.c:83 [inline]
atomic_notifier_call_chain+0x15d/0x280 kernel/notifier.c:198
notify_die+0x12d/0x180 kernel/notifier.c:529
notify_debug+0x20/0x30 arch/x86/kernel/traps.c:872
exc_debug_kernel arch/x86/kernel/traps.c:929 [inline]
exc_debug+0xcf/0x130 arch/x86/kernel/traps.c:1029
asm_exc_debug+0x1a/0x40 arch/x86/include/asm/idtentry.h:642
RIP: 0010:copy_user_enhanced_fast_string+0xe/0x40 arch/x86/lib/copy_user_64.S:206
Code: 89 d1 c1 e9 03 83 e2 07 f3 48 a5 89 d1 f3 a4 31 c0 0f 01 ca c3 90 90 90 90 90 90 90 0f 01 cb 83 fa 40 0f 82 70 ff ff ff 89 d1 <f3> a4 31 c0 0f 01 ca c3 90 90 90 90 90 90 90 90 90 90 89 d1 83 f8
RSP: 0018:ffffc900010cfb78 EFLAGS: 00050202
RAX: ffffffff83daed01 RBX: 0000000000000078 RCX: 0000000000000036
RDX: 0000000000000078 RSI: 0000200000000302 RDI: ffffc90000e4608a
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff520001c8c18
R10: fffff520001c8c18 R11: 1ffff920001c8c09 R12: 00007ffffffff000
R13: 0000200000000338 R14: ffffc90000e46048 R15: 00002000000002c0
</#DB>
<TASK>
copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
raw_copy_from_user arch/x86/include/asm/uaccess_64.h:52 [inline]
_copy_from_user+0xfa/0x170 lib/usercopy.c:23
copy_from_user include/linux/uaccess.h:192 [inline]
copy_from_bpfptr_offset include/linux/bpfptr.h:52 [inline]
copy_from_bpfptr+0x67/0x80 include/linux/bpfptr.h:58
bpf_prog_load+0xb1c/0x1550 kernel/bpf/syscall.c:2325
__sys_bpf+0x4c2/0x670 kernel/bpf/syscall.c:4657
__do_sys_bpf kernel/bpf/syscall.c:4761 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4759 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4759
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fde7c3d3749
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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffccba3b8c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007fde7c629fa0 RCX: 00007fde7c3d3749
RDX: 0000000000000094 RSI: 00002000000007c0 RDI: 0000000000000005
RBP: 00007fde7c457f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fde7c629fa0 R14: 00007fde7c629fa0 R15: 0000000000000003
</TASK>
----------------
Code disassembly (best guess):
0: 89 d1 mov %edx,%ecx
2: c1 e9 03 shr $0x3,%ecx
5: 83 e2 07 and $0x7,%edx
8: f3 48 a5 rep movsq %ds:(%rsi),%es:(%rdi)
b: 89 d1 mov %edx,%ecx
d: f3 a4 rep movsb %ds:(%rsi),%es:(%rdi)
f: 31 c0 xor %eax,%eax
11: 0f 01 ca clac
14: c3 ret
15: 90 nop
16: 90 nop
17: 90 nop
18: 90 nop
19: 90 nop
1a: 90 nop
1b: 90 nop
1c: 0f 01 cb stac
1f: 83 fa 40 cmp $0x40,%edx
22: 0f 82 70 ff ff ff jb 0xffffff98
28: 89 d1 mov %edx,%ecx
* 2a: f3 a4 rep movsb %ds:(%rsi),%es:(%rdi) <-- trapping instruction
2c: 31 c0 xor %eax,%eax
2e: 0f 01 ca clac
31: c3 ret
32: 90 nop
33: 90 nop
34: 90 nop
35: 90 nop
36: 90 nop
37: 90 nop
38: 90 nop
39: 90 nop
3a: 90 nop
3b: 90 nop
3c: 89 d1 mov %edx,%ecx
3e: 83 .byte 0x83
3f: f8 clc


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup