From: syzbot <syzbot+d451401ffd00a60677ee@syzkaller.appspotmail.com>
To: davem@davemloft.net, johannes@sipsolutions.net,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: WARNING in restore_regulatory_settings
Date: Mon, 06 Jan 2020 12:54:12 -0800 [thread overview]
Message-ID: <00000000000093b204059b7edce0@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: c79f46a2 Linux 5.5-rc5
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1357513ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=42c82694f792b2f5
dashboard link: https://syzkaller.appspot.com/bug?extid=d451401ffd00a60677ee
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11538115e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11d6ee3ee00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d451401ffd00a60677ee@syzkaller.appspotmail.com
------------[ cut here ]------------
Unexpected user alpha2: \0\0
WARNING: CPU: 0 PID: 2810 at net/wireless/reg.c:418 is_user_regdom_saved
net/wireless/reg.c:418 [inline]
WARNING: CPU: 0 PID: 2810 at net/wireless/reg.c:418 restore_alpha2
net/wireless/reg.c:3092 [inline]
WARNING: CPU: 0 PID: 2810 at net/wireless/reg.c:418
restore_regulatory_settings+0x226/0x13e0 net/wireless/reg.c:3184
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 2810 Comm: kworker/0:55 Not tainted 5.5.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: events_power_efficient crda_timeout_work
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x197/0x210 lib/dump_stack.c:118
panic+0x2e3/0x75c kernel/panic.c:221
__warn.cold+0x2f/0x3e kernel/panic.c:582
report_bug+0x289/0x300 lib/bug.c:195
fixup_bug arch/x86/kernel/traps.c:174 [inline]
fixup_bug arch/x86/kernel/traps.c:169 [inline]
do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:267
do_invalid_op+0x37/0x50 arch/x86/kernel/traps.c:286
invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1027
RIP: 0010:is_user_regdom_saved net/wireless/reg.c:418 [inline]
RIP: 0010:restore_alpha2 net/wireless/reg.c:3092 [inline]
RIP: 0010:restore_regulatory_settings+0x226/0x13e0 net/wireless/reg.c:3184
Code: 03 44 89 f6 e8 2b ba 1f fa 45 84 f6 0f 85 9a 07 00 00 e8 dd b8 1f fa
41 0f be d5 0f be f3 48 c7 c7 00 ba ed 88 e8 f9 60 f0 f9 <0f> 0b e8 c3 b8
1f fa 4c 8b 2d 6c e2 12 03 48 b8 00 00 00 00 00 fc
RSP: 0018:ffffc900080dfc20 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff815e8b46 RDI: fffff5200101bf76
RBP: ffffc900080dfd20 R08: ffff88809f6ca080 R09: ffffed1015d06621
R10: ffffed1015d06620 R11: ffff8880ae833107 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000000 R15: ffff8880ae836b40
crda_timeout_work+0x21/0x30 net/wireless/reg.c:520
process_one_work+0x9af/0x1740 kernel/workqueue.c:2264
worker_thread+0x98/0xe40 kernel/workqueue.c:2410
kthread+0x361/0x430 kernel/kthread.c:255
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2020-01-06 21:01 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=00000000000093b204059b7edce0@google.com \
--to=syzbot+d451401ffd00a60677ee@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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.