======================================================
WARNING: possible circular locking dependency detected
5.14.0-rc2-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.3/6008 is trying to acquire lock:
ffffffff8c4a8d88 (rtnl_mutex){+.+.}-{3:3}, at: br_del_bridge+0xe/0xd0 net/bridge/br_if.c:470

but task is already holding lock:
ffffffff8c4885a8 (br_ioctl_mutex){+.+.}-{3:3}, at: br_ioctl_call+0x2f/0x90 net/socket.c:1089

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (br_ioctl_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:959 [inline]
       __mutex_lock+0x12a/0x10a0 kernel/locking/mutex.c:1104
       br_ioctl_call+0x2f/0x90 net/socket.c:1089
       dev_ifsioc+0x8d6/0xc80 net/core/dev_ioctl.c:382
       dev_ioctl+0x14c/0xc70 net/core/dev_ioctl.c:580
       sock_do_ioctl+0x150/0x1a0 net/socket.c:1128
       sock_ioctl+0x278/0x510 net/socket.c:1231
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:1069 [inline]
       __se_sys_ioctl fs/ioctl.c:1055 [inline]
       __x64_sys_ioctl+0x11f/0x190 fs/ioctl.c:1055
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x35/0x80 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x44/0xae

-> #0 (rtnl_mutex){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3051 [inline]
       check_prevs_add kernel/locking/lockdep.c:3174 [inline]
       validate_chain kernel/locking/lockdep.c:3789 [inline]
       __lock_acquire+0x2985/0x5410 kernel/locking/lockdep.c:5015
       lock_acquire kernel/locking/lockdep.c:5625 [inline]
       lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5590
       __mutex_lock_common kernel/locking/mutex.c:959 [inline]
       __mutex_lock+0x12a/0x10a0 kernel/locking/mutex.c:1104
       br_del_bridge+0xe/0xd0 net/bridge/br_if.c:470
       br_ioctl_stub+0x288/0x630 net/bridge/br_ioctl.c:392
       br_ioctl_call+0x4c/0x90 net/socket.c:1091
       sock_ioctl+0x28e/0x510 net/socket.c:1185
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:1069 [inline]
       __se_sys_ioctl fs/ioctl.c:1055 [inline]
       __x64_sys_ioctl+0x11f/0x190 fs/ioctl.c:1055
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x35/0x80 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x44/0xae

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(br_ioctl_mutex);
                               lock(rtnl_mutex);
                               lock(br_ioctl_mutex);
  lock(rtnl_mutex);

 *** DEADLOCK ***

1 lock held by syz-executor.3/6008:
 #0: ffffffff8c4885a8 (br_ioctl_mutex){+.+.}-{3:3}, at: br_ioctl_call+0x2f/0x90 net/socket.c:1089

stack backtrace:
CPU: 1 PID: 6008 Comm: syz-executor.3 Not tainted 5.14.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Call Trace:
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x57/0x7d lib/dump_stack.c:105
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2131
 check_prev_add kernel/locking/lockdep.c:3051 [inline]
 check_prevs_add kernel/locking/lockdep.c:3174 [inline]
 validate_chain kernel/locking/lockdep.c:3789 [inline]
 __lock_acquire+0x2985/0x5410 kernel/locking/lockdep.c:5015
 lock_acquire kernel/locking/lockdep.c:5625 [inline]
 lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5590
 __mutex_lock_common kernel/locking/mutex.c:959 [inline]
 __mutex_lock+0x12a/0x10a0 kernel/locking/mutex.c:1104
 br_del_bridge+0xe/0xd0 net/bridge/br_if.c:470
 br_ioctl_stub+0x288/0x630 net/bridge/br_ioctl.c:392
 br_ioctl_call+0x4c/0x90 net/socket.c:1091
 sock_ioctl+0x28e/0x510 net/socket.c:1185
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:1069 [inline]
 __se_sys_ioctl fs/ioctl.c:1055 [inline]
 __x64_sys_ioctl+0x11f/0x190 fs/ioctl.c:1055
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0x80 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7fd6af5bd169
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fd6ae92f168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fd6af6dcf80 RCX: 00007fd6af5bd169
RDX: 0000000020000080 RSI: 00000000000089a1 RDI: 0000000000000004
RBP: 00007fd6af618ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffd633722f R14: 00007fd6ae92f300 R15: 0000000000022000
device bridge_slave_1 left promiscuous mode
bridge0: port 2(bridge_slave_1) entered disabled state
device bridge_slave_0 left promiscuous mode
bridge0: port 1(bridge_slave_0) entered disabled state