[v6.6] BUG: MAX_STACK_TRACE_ENTRIES too low!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: af1544b5d072 Linux 6.6.107
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13f284e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=e727758e2a57bcf22bcd
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=14b698e2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1565627c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2ed6542fdd63/disk-af1544b5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dd817ab10eaa/vmlinux-af1544b5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b6e6807cd6c1/bzImage-af1544b5.xz

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

BUG: MAX_STACK_TRACE_ENTRIES too low!
turning off the locking correctness validator.
CPU: 0 PID: 5158 Comm: udevd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
save_trace+0x991/0xcd0 kernel/locking/lockdep.c:578
check_prev_add kernel/locking/lockdep.c:3195 [inline]
check_prevs_add kernel/locking/lockdep.c:3253 [inline]
validate_chain kernel/locking/lockdep.c:3869 [inline]
__lock_acquire+0x4399/0x7c80 kernel/locking/lockdep.c:5137
lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
htab_lock_bucket+0x181/0x300 kernel/bpf/hashtab.c:166
htab_lru_map_delete_elem+0x1a4/0x630 kernel/bpf/hashtab.c:1479
bpf_prog_e15fd5db8382a83f+0x63/0x67
bpf_dispatcher_nop_func include/linux/bpf.h:1223 [inline]
__bpf_prog_run include/linux/filter.h:612 [inline]
bpf_prog_run include/linux/filter.h:619 [inline]
__bpf_trace_run kernel/trace/bpf_trace.c:2322 [inline]
bpf_trace_run2+0x1d1/0x3c0 kernel/trace/bpf_trace.c:2361
__traceiter_kfree+0x2a/0x40 include/trace/events/kmem.h:94
trace_kfree include/trace/events/kmem.h:94 [inline]
kfree+0xf8/0x1a0 mm/slab_common.c:1043
kernfs_fop_write_iter+0x458/0x520 fs/kernfs/file.c:366
call_write_iter include/linux/fs.h:2018 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x43b/0x940 fs/read_write.c:584
ksys_write+0x147/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f89e80a7407
Code: 48 89 fa 4c 89 df e8 38 aa 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff
RSP: 002b:00007ffc78fb9800 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f89e8788880 RCX: 00007f89e80a7407
RDX: 0000000000000007 RSI: 0000559dcb2c8f90 RDI: 000000000000000c
RBP: 0000559dcb2c8f90 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000007
R13: 0000559dcb2a3a90 R14: 00007f89e81efea0 R15: 00007ffc78fb9b40
</TASK>


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