============================================ WARNING: possible recursive locking detected 6.9.0-syzkaller-12162-gf85af9d955ac #0 Not tainted -------------------------------------------- syz-executor.0/5108 is trying to acquire lock: ffff88802ae29a20 (&stab->lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline] ffff88802ae29a20 (&stab->lock){+.-.}-{2:2}, at: __sock_map_delete net/core/sock_map.c:429 [inline] ffff88802ae29a20 (&stab->lock){+.-.}-{2:2}, at: sock_map_delete_elem+0x175/0x250 net/core/sock_map.c:461 but task is already holding lock: ffff88802ae2a220 (&stab->lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline] ffff88802ae2a220 (&stab->lock){+.-.}-{2:2}, at: __sock_map_delete net/core/sock_map.c:429 [inline] ffff88802ae2a220 (&stab->lock){+.-.}-{2:2}, at: sock_map_delete_elem+0x175/0x250 net/core/sock_map.c:461 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&stab->lock); lock(&stab->lock); *** DEADLOCK *** May be due to missing lock nesting notation 9 locks held by syz-executor.0/5108: #0: ffff888030478420 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:409 #1: ffff88807e2f5e00 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:826 [inline] #1: ffff88807e2f5e00 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: do_rmdir+0x263/0x580 fs/namei.c:4261 #2: ffff888030478610 (sb_internal){.+.+}-{0:0}, at: __sb_start_write include/linux/fs.h:1655 [inline] #2: ffff888030478610 (sb_internal){.+.+}-{0:0}, at: sb_start_intwrite include/linux/fs.h:1838 [inline] #2: ffff888030478610 (sb_internal){.+.+}-{0:0}, at: ext4_evict_inode+0x2f4/0xf50 fs/ext4/inode.c:212 #3: ffff88803047c950 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x203f/0x22a0 fs/jbd2/transaction.c:463 #4: ffff8880421d8288 (&ei->i_data_sem){++++}-{3:3}, at: ext4_truncate+0x991/0x1180 fs/ext4/inode.c:4134 #5: ffffffff8e333e60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline] #5: ffffffff8e333e60 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:781 [inline] #5: ffffffff8e333e60 (rcu_read_lock){....}-{1:2}, at: __bpf_trace_run kernel/trace/bpf_trace.c:2402 [inline] #5: ffffffff8e333e60 (rcu_read_lock){....}-{1:2}, at: bpf_trace_run6+0x2a5/0x600 kernel/trace/bpf_trace.c:2448 #6: ffff88802ae2a220 (&stab->lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline] #6: ffff88802ae2a220 (&stab->lock){+.-.}-{2:2}, at: __sock_map_delete net/core/sock_map.c:429 [inline] #6: ffff88802ae2a220 (&stab->lock){+.-.}-{2:2}, at: sock_map_delete_elem+0x175/0x250 net/core/sock_map.c:461 #7: ffff88806172e2b0 (&psock->link_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline] #7: ffff88806172e2b0 (&psock->link_lock){+...}-{2:2}, at: sock_map_del_link net/core/sock_map.c:157 [inline] #7: ffff88806172e2b0 (&psock->link_lock){+...}-{2:2}, at: sock_map_unref+0xcc/0x5e0 net/core/sock_map.c:192 #8: ffffffff8e333e60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline] #8: ffffffff8e333e60 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:781 [inline] #8: ffffffff8e333e60 (rcu_read_lock){....}-{1:2}, at: __bpf_trace_run kernel/trace/bpf_trace.c:2402 [inline] #8: ffffffff8e333e60 (rcu_read_lock){....}-{1:2}, at: bpf_trace_run2+0x1fc/0x540 kernel/trace/bpf_trace.c:2444 stack backtrace: CPU: 0 PID: 5108 Comm: syz-executor.0 Not tainted 6.9.0-syzkaller-12162-gf85af9d955ac #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 check_deadlock kernel/locking/lockdep.c:3062 [inline] validate_chain+0x15d3/0x5900 kernel/locking/lockdep.c:3856 __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5137 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5754 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline] _raw_spin_lock_bh+0x35/0x50 kernel/locking/spinlock.c:178