[v6.1] WARNING in drv_remove_interface

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 75389113731b Linux 6.1.40
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12c509e6a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9027f9f0abc1e82f
dashboard link: https://syzkaller.appspot.com/bug?extid=f8860595b53145f66696
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8579f6cd3c5c/disk-75389113.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cf95e75287e2/vmlinux-75389113.xz
kernel image: https://storage.googleapis.com/syzbot-assets/479ef4915330/bzImage-75389113.xz

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

------------[ cut here ]------------
wlan1: Failed check-sdata-in-driver check, flags: 0x1
WARNING: CPU: 1 PID: 31304 at net/mac80211/driver-ops.c:98 drv_remove_interface+0x1f8/0x410 net/mac80211/driver-ops.c:98
Modules linked in:
CPU: 1 PID: 31304 Comm: syz-executor.5 Not tainted 6.1.40-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
RIP: 0010:drv_remove_interface+0x1f8/0x410 net/mac80211/driver-ops.c:98
Code: be 4e e3 f7 49 8b 87 08 09 00 00 49 81 c7 28 09 00 00 48 85 c0 4c 0f 45 f8 48 c7 c7 a0 12 fc 8b 4c 89 fe 89 ea e8 e8 58 55 f7 <0f> 0b e9 7d fe ff ff e8 ac e9 8c f7 0f 0b e9 c7 fe ff ff e8 a0 e9
RSP: 0000:ffffc90004db6900 EFLAGS: 00010246
RAX: 7a957e99b7897700 RBX: dffffc0000000000 RCX: 0000000000040000
RDX: ffffc9000d0ec000 RSI: 0000000000005c41 RDI: 0000000000005c42
RBP: 0000000000000001 R08: ffffffff81524cae R09: fffff520009b6c99
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888079c49598
R13: 1ffff1100f3892b3 R14: ffff8880768a8de0 R15: ffff888079c48000
FS: 00007f94eee2f6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb50c7eb000 CR3: 0000000039c9e000 CR4: 00000000003506e0
DR0: 00000000ffff070c DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_do_stop+0x153c/0x1d50 net/mac80211/iface.c:694
ieee80211_stop+0x410/0x480 net/mac80211/iface.c:762
__dev_close_many+0x2db/0x3c0 net/core/dev.c:1516
__dev_close net/core/dev.c:1528 [inline]
__dev_change_flags+0x2fe/0x6e0 net/core/dev.c:8548
dev_change_flags+0x87/0x190 net/core/dev.c:8621
do_setlink+0xf5d/0x3e60 net/core/rtnetlink.c:2794
__rtnl_newlink net/core/rtnetlink.c:3559 [inline]
rtnl_newlink+0x16f7/0x1fa0 net/core/rtnetlink.c:3606
rtnetlink_rcv_msg+0x776/0xf00 net/core/rtnetlink.c:6103
netlink_rcv_skb+0x1cd/0x410 net/netlink/af_netlink.c:2525
netlink_unicast_kernel net/netlink/af_netlink.c:1328 [inline]
netlink_unicast+0x7bf/0x990 net/netlink/af_netlink.c:1354
netlink_sendmsg+0xa26/0xd60 net/netlink/af_netlink.c:1903
sock_sendmsg_nosec net/socket.c:716 [inline]
sock_sendmsg net/socket.c:736 [inline]
____sys_sendmsg+0x59e/0x8f0 net/socket.c:2482
___sys_sendmsg net/socket.c:2536 [inline]
__sys_sendmsg+0x2a9/0x390 net/socket.c:2565
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f94ee07cb29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f94eee2f0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f94ee19bf80 RCX: 00007f94ee07cb29
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000000000004
RBP: 00007f94ee0c847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f94ee19bf80 R15: 00007ffc404da778
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.