Hello,
syzbot found the following issue on:
HEAD commit: 4143d798 Linux 4.19.165
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=105750af500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=250ed6957c7993a3
dashboard link:
https://syzkaller.appspot.com/bug?extid=25057181cc067c9e92c5
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+250571...@syzkaller.appspotmail.com
WARNING: CPU: 0 PID: 8530 at net/mac80211/offchannel.c:419 ieee80211_start_next_roc+0x1ed/0x240 net/mac80211/offchannel.c:419
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 8530 Comm: syz-executor.1 Not tainted 4.19.165-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:ieee80211_start_next_roc+0x1ed/0x240 net/mac80211/offchannel.c:419
Code: 58 16 00 00 48 89 ef 48 89 c2 e8 2e 06 0b 00 5b 5d e9 97 f1 ab f9 e8 92 f1 ab f9 48 89 ef e8 7a 6b ff ff eb 94 e8 83 f1 ab f9 <0f> 0b eb 8b e8 ea 17 e2 f9 e9 be fe ff ff 48 c7 c7 40 cc 45 8a e8
RSP: 0000:ffff8880454c7318 EFLAGS: 00010216
RAX: 0000000000040000 RBX: 0000000000000001 RCX: ffffc90007d48000
RDX: 0000000000002089 RSI: ffffffff87b8df8d RDI: 0000000000000001
RBP: ffff88804a839a60 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000001 R14: dffffc0000000000 R15: ffff88804a83a900
__ieee80211_scan_completed+0x571/0x1690 net/mac80211/scan.c:442
ieee80211_scan_cancel+0x340/0x940 net/mac80211/scan.c:1168
ieee80211_do_stop+0x18c6/0x1ff0 net/mac80211/iface.c:813
ieee80211_runtime_change_iftype net/mac80211/iface.c:1545 [inline]
ieee80211_if_change_type+0x29f/0x5f0 net/mac80211/iface.c:1579
ieee80211_change_iface+0x26/0x220 net/mac80211/cfg.c:157
rdev_change_virtual_intf net/wireless/rdev-ops.h:69 [inline]
cfg80211_change_iface+0x2e1/0x1530 net/wireless/util.c:936
nl80211_set_interface+0x661/0x830 net/wireless/nl80211.c:3205
genl_family_rcv_msg+0x642/0xc40 net/netlink/genetlink.c:602
genl_rcv_msg+0xbf/0x160 net/netlink/genetlink.c:627
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2455
genl_rcv+0x24/0x40 net/netlink/genetlink.c:638
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6bb/0xc40 net/netlink/af_netlink.c:1909
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:632
___sys_sendmsg+0x7bb/0x8e0 net/socket.c:2115
__sys_sendmsg net/socket.c:2153 [inline]
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2160
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45e219
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f0c7d24dc68 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045e219
RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003
RBP: 000000000119bfc0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000119bf8c
R13: 00007ffee7b8c4df R14: 00007f0c7d24e9c0 R15: 000000000119bf8c
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.