divide error in mac80211_hwsim_bss_info_changed

7 views
Skip to first unread message

syzbot

unread,
Oct 5, 2020, 10:02:18 AM10/5/20
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9d0d6300 ANDROID: use arm-linux-androidkernel- for CROSS_C..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=10c7d83b900000
kernel config: https://syzkaller.appspot.com/x/.config?x=889e2c88a7f30f62
dashboard link: https://syzkaller.appspot.com/bug?extid=14e60354edce3ae858fb
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)

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+14e603...@syzkaller.appspotmail.com

divide error: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 30880 Comm: kworker/u4:10 Tainted: G W 5.4.69-syzkaller-00867-g9d0d630081ae #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: phy49 ieee80211_roc_work
RIP: 0010:mac80211_hwsim_bss_info_changed+0x3df/0x800 drivers/net/wireless/mac80211_hwsim.c:1759
Code: 00 fc ff df 48 81 44 24 20 40 13 00 00 49 03 1f 41 80 7c 0d 00 00 74 08 4c 89 f7 e8 0b ba ec fe 49 8b 0e 89 ce 48 89 d8 31 d2 <48> f7 f6 29 d1 48 69 f1 e8 03 00 00 48 8b 7c 24 20 31 d2 b9 05 00
RSP: 0018:ffff8881d9137b20 EFLAGS: 00010246
RAX: 0005b0eceb1631bd RBX: 0005b0eceb1631bd RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8881d9137be8 R08: ffffffff81331dc6 R09: ffffffff83a6a74d
R10: ffff8881c490ae80 R11: 0000000000000003 R12: ffff8881c4634970
R13: 1ffff110388c6e4a R14: ffff8881c4637250 R15: ffff8881c4637308
FS: 0000000000000000(0000) GS:ffff8881db800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0accdebdb8 CR3: 00000001b5fd4006 CR4: 00000000001606f0
DR0: 0000000020000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
drv_bss_info_changed+0x32d/0x580 net/mac80211/driver-ops.h:178
ieee80211_offchannel_return+0x39b/0x500 net/mac80211/offchannel.c:178
__ieee80211_roc_work+0x4a6/0x680 net/mac80211/offchannel.c:464
ieee80211_roc_work+0x29/0x40 net/mac80211/offchannel.c:478
process_one_work+0x777/0xf90 kernel/workqueue.c:2276
worker_thread+0xa8f/0x1430 kernel/workqueue.c:2422
kthread+0x317/0x340 kernel/kthread.c:268
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:352
Modules linked in:
---[ end trace 24268a74cb011ffe ]---
RIP: 0010:mac80211_hwsim_bss_info_changed+0x3df/0x800 drivers/net/wireless/mac80211_hwsim.c:1759
Code: 00 fc ff df 48 81 44 24 20 40 13 00 00 49 03 1f 41 80 7c 0d 00 00 74 08 4c 89 f7 e8 0b ba ec fe 49 8b 0e 89 ce 48 89 d8 31 d2 <48> f7 f6 29 d1 48 69 f1 e8 03 00 00 48 8b 7c 24 20 31 d2 b9 05 00
RSP: 0018:ffff8881d9137b20 EFLAGS: 00010246
RAX: 0005b0eceb1631bd RBX: 0005b0eceb1631bd RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff8881d9137be8 R08: ffffffff81331dc6 R09: ffffffff83a6a74d
R10: ffff8881c490ae80 R11: 0000000000000003 R12: ffff8881c4634970
R13: 1ffff110388c6e4a R14: ffff8881c4637250 R15: ffff8881c4637308
FS: 0000000000000000(0000) GS:ffff8881db800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0accdebdb8 CR3: 00000001b5fd4006 CR4: 00000000001606f0
DR0: 0000000020000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600


---
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

unread,
Feb 9, 2021, 6:56:12 PM2/9/21
to syzkaller-a...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages