From: syzbot <syzbot+92715a0eccd6c881bc32@syzkaller.appspotmail.com>
To: davem@davemloft.net, johannes.berg@intel.com,
johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
thomas@adapt-ip.com
Subject: WARNING in ieee80211_s1g_channel_width
Date: Mon, 05 Oct 2020 01:48:24 -0700 [thread overview]
Message-ID: <000000000000a04cf205b0e88bb3@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 678cdd49 Merge branch 'genetlink-support-per-command-polic..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=158bb760500000
kernel config: https://syzkaller.appspot.com/x/.config?x=1e6c5266df853ae
dashboard link: https://syzkaller.appspot.com/bug?extid=92715a0eccd6c881bc32
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12ac92af900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15bcb733900000
The issue was bisected to:
commit 11b34737b18a70c74d5cf13ee58d36e95879013c
Author: Thomas Pedersen <thomas@adapt-ip.com>
Date: Tue Sep 8 19:03:06 2020 +0000
nl80211: support setting S1G channels
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=128cbf7b900000
final oops: https://syzkaller.appspot.com/x/report.txt?x=118cbf7b900000
console output: https://syzkaller.appspot.com/x/log.txt?x=168cbf7b900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+92715a0eccd6c881bc32@syzkaller.appspotmail.com
Fixes: 11b34737b18a ("nl80211: support setting S1G channels")
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6864 at net/wireless/util.c:117 ieee80211_s1g_channel_width+0x51/0x180 net/wireless/util.c:117
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 6864 Comm: syz-executor803 Not tainted 5.9.0-rc6-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+0x198/0x1fd lib/dump_stack.c:118
panic+0x382/0x7fb kernel/panic.c:231
__warn.cold+0x20/0x4b kernel/panic.c:600
report_bug+0x1bd/0x210 lib/bug.c:198
handle_bug+0x38/0x90 arch/x86/kernel/traps.c:234
exc_invalid_op+0x14/0x40 arch/x86/kernel/traps.c:254
asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:536
RIP: 0010:ieee80211_s1g_channel_width+0x51/0x180 net/wireless/util.c:117
Code: ea 03 0f b6 04 02 84 c0 74 08 3c 03 0f 8e 34 01 00 00 8b 2b bf 04 00 00 00 89 ee e8 59 13 c1 f9 83 fd 04 74 19 e8 ef 16 c1 f9 <0f> 0b 45 31 e4 e8 e5 16 c1 f9 44 89 e0 5b 5d 41 5c 41 5d c3 e8 d6
RSP: 0018:ffffc900044172d0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff8882179037d0 RCX: ffffffff87b570b7
RDX: ffff88808dc361c0 RSI: ffffffff87b570c1 RDI: 0000000000000005
RBP: 0000000000000001 R08: 0000000000000001 R09: ffffc900044173f8
R10: 0000000000000004 R11: 1ffffffff19a4e5d R12: 0000000000000000
R13: 000000000000148c R14: 0000000000000000 R15: ffffc90004417404
cfg80211_chandef_valid+0x222/0xc30 net/wireless/chan.c:227
nl80211_parse_chandef+0x5ed/0xdf0 net/wireless/nl80211.c:2979
__nl80211_set_channel+0x2e3/0x860 net/wireless/nl80211.c:3016
nl80211_set_wiphy+0xa6c/0x2d40 net/wireless/nl80211.c:3189
genl_family_rcv_msg_doit+0x228/0x320 net/netlink/genetlink.c:739
genl_family_rcv_msg net/netlink/genetlink.c:783 [inline]
genl_rcv_msg+0x518/0x940 net/netlink/genetlink.c:800
netlink_rcv_skb+0x15a/0x430 net/netlink/af_netlink.c:2489
genl_rcv+0x24/0x40 net/netlink/genetlink.c:811
netlink_unicast_kernel net/netlink/af_netlink.c:1304 [inline]
netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1330
netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1919
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:671
____sys_sendmsg+0x6e8/0x810 net/socket.c:2353
___sys_sendmsg+0xf3/0x170 net/socket.c:2407
__sys_sendmsg+0xe5/0x1b0 net/socket.c:2440
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x440979
Code: 18 89 d0 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 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 5b 11 fc ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffc9e2880d8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 0000000000440979
RDX: 0000000000000000 RSI: 0000000020001f40 RDI: 0000000000000003
RBP: 00000000006ca018 R08: 0000000000000008 R09: 00000000004002c8
R10: 0000000000000026 R11: 0000000000000246 R12: 0000000000401f60
R13: 0000000000401ff0 R14: 0000000000000000 R15: 0000000000000000
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2020-10-05 8:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000a04cf205b0e88bb3@google.com \
--to=syzbot+92715a0eccd6c881bc32@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=thomas@adapt-ip.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.