WARNING in drv_remove_interface

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b94de4d1 Linux 4.19.155
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12894746500000
kernel config: https://syzkaller.appspot.com/x/.config?x=252047157acf1cb1
dashboard link: https://syzkaller.appspot.com/bug?extid=f0815793cfb8b9ac09ca
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1219ac3a500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=122dbb46500000

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

syz-executor120 uses obsolete (PF_INET,SOCK_PACKET)
------------[ cut here ]------------
wlan0: Failed check-sdata-in-driver check, flags: 0x0
WARNING: CPU: 0 PID: 8121 at net/mac80211/driver-ops.h:17 check_sdata_in_driver net/mac80211/driver-ops.h:17 [inline]
WARNING: CPU: 0 PID: 8121 at net/mac80211/driver-ops.h:17 drv_remove_interface+0x56e/0x710 net/mac80211/driver-ops.c:100
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8121 Comm: syz-executor120 Not tainted 4.19.155-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x61 kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:check_sdata_in_driver net/mac80211/driver-ops.h:17 [inline]
RIP: 0010:drv_remove_interface+0x56e/0x710 net/mac80211/driver-ops.c:100
Code: 00 00 48 85 db 0f 84 f9 00 00 00 e8 8c dd af f9 48 89 dd e8 84 dd af f9 44 89 ea 48 89 ee 48 c7 c7 e0 8c 66 89 e8 bd bb 83 f9 <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f e9 61 dd af f9 e8 5c dd af f9
RSP: 0018:ffff8880b12975b8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff8880abb14500 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814fda81 RDI: ffffed1016252ea9
RBP: ffff8880abb14500 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8882387a8ba0
R13: 0000000000000000 R14: ffff8880abb154f8 R15: 000000000000000f
ieee80211_do_stop+0x114e/0x1ff0 net/mac80211/iface.c:1053
ieee80211_stop+0x1a/0x20 net/mac80211/iface.c:1080
__dev_close_many+0x1ab/0x2e0 net/core/dev.c:1485
__dev_close net/core/dev.c:1497 [inline]
__dev_change_flags+0x273/0x660 net/core/dev.c:7669
dev_change_flags+0x7e/0x140 net/core/dev.c:7740
devinet_ioctl+0x13c9/0x1b40 net/ipv4/devinet.c:1106
inet_ioctl+0x1ea/0x360 net/ipv4/af_inet.c:954
packet_ioctl+0xb9/0x2b0 net/packet/af_packet.c:4149
sock_do_ioctl+0xcb/0x2d0 net/socket.c:950
sock_ioctl+0x2ef/0x5d0 net/socket.c:1074
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x447169
Code: e8 5c b1 02 00 48 83 c4 18 c3 0f 1f 80 00 00 00 00 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 0f 83 6b 05 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f9a94e7bd98 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006dcc48 RCX: 0000000000447169
RDX: 0000000020001000 RSI: 0000000000008914 RDI: 0000000000000003
RBP: 00000000006dcc40 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000006dcc4c
R13: 0000000000000000 R14: 000000306e616c77 R15: 0000000000000fb0
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches