ODEBUG: Out of memory. ODEBUG disabled
======================================================
WARNING: possible circular locking dependency detected
5.15.160-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.0/5074 is trying to acquire lock:
ffffffff8c914660 (console_owner){-...}-{0:0}, at: console_trylock_spinning+0x185/0x3f0 kernel/printk/printk.c:1879

but task is already holding lock:
ffff88801cb549b8 (&trie->lock){..-.}-{2:2}, at: trie_update_elem+0xc5/0xc00 kernel/bpf/lpm_trie.c:323

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&trie->lock){..-.}-{2:2}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
       _raw_spin_lock_irqsave+0xd1/0x120 kernel/locking/spinlock.c:162
       trie_delete_elem+0x90/0x690 kernel/bpf/lpm_trie.c:450
       0xffffffffa002c118
       bpf_dispatcher_nop_func include/linux/bpf.h:790 [inline]
       __bpf_prog_run include/linux/filter.h:628 [inline]
       bpf_prog_run include/linux/filter.h:635 [inline]
       __bpf_trace_run kernel/trace/bpf_trace.c:1880 [inline]
       bpf_trace_run2+0x19e/0x340 kernel/trace/bpf_trace.c:1917
       trace_console_rcuidle include/trace/events/printk.h:10 [inline]
       call_console_drivers kernel/printk/printk.c:1932 [inline]
       console_unlock+0x10a2/0x12b0 kernel/printk/printk.c:2744
       vprintk_emit+0xbf/0x150 kernel/printk/printk.c:2274
       _printk+0xd1/0x120 kernel/printk/printk.c:2299
       __ext4_warning+0x200/0x210 fs/ext4/super.c:939
       verify_group_input fs/ext4/resize.c:146 [inline]
       ext4_group_add+0x790/0x1570 fs/ext4/resize.c:1707
       ext4_ioctl_group_add+0x161/0x510 fs/ext4/ioctl.c:710
       __ext4_ioctl fs/ext4/ioctl.c:1009 [inline]
       ext4_ioctl+0x17cc/0x5b80 fs/ext4/ioctl.c:1276
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (console_owner){-...}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788
       __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       console_trylock_spinning+0x1a5/0x3f0 kernel/printk/printk.c:1896
       vprintk_emit+0xa6/0x150 kernel/printk/printk.c:2273
       _printk+0xd1/0x120 kernel/printk/printk.c:2299
       debug_objects_oom+0xb4/0x370 lib/debugobjects.c:472
       debug_object_activate+0x42d/0x4e0 lib/debugobjects.c:698
       debug_rcu_head_queue kernel/rcu/rcu.h:176 [inline]
       kvfree_call_rcu+0xb6/0x8a0 kernel/rcu/tree.c:3587
       trie_update_elem+0x808/0xc00 kernel/bpf/lpm_trie.c:384
       bpf_map_update_value+0x5d7/0x6c0 kernel/bpf/syscall.c:221
       generic_map_update_batch+0x54d/0x8b0 kernel/bpf/syscall.c:1421
       bpf_map_do_batch+0x4d0/0x620
       __sys_bpf+0x55c/0x670
       __do_sys_bpf kernel/bpf/syscall.c:4755 [inline]
       __se_sys_bpf kernel/bpf/syscall.c:4753 [inline]
       __x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4753
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&trie->lock);
                               lock(console_owner);
                               lock(&trie->lock);
  lock(console_owner);

 *** DEADLOCK ***

2 locks held by syz-executor.0/5074:
 #0: ffffffff8c91fae0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:311
 #1: ffff88801cb549b8 (&trie->lock){..-.}-{2:2}, at: trie_update_elem+0xc5/0xc00 kernel/bpf/lpm_trie.c:323

stack backtrace:
CPU: 1 PID: 5074 Comm: syz-executor.0 Not tainted 5.15.160-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x2f8/0x3b0 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788