From: syzbot <syzbot+c6f3c081bf956c97e4de@syzkaller.appspotmail.com>
To: johannes@sipsolutions.net, kvalo@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [wireless?] divide error in mac80211_hwsim_link_info_changed
Date: Thu, 18 Jul 2024 01:46:23 -0700 [thread overview]
Message-ID: <000000000000152438061d819d0b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 51835949dda3 Merge tag 'net-next-6.11' of git://git.kernel..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15f207a5980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d3bdd09ea2371c89
dashboard link: https://syzkaller.appspot.com/bug?extid=c6f3c081bf956c97e4de
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9690deac1819/disk-51835949.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/54d261dbb3f0/vmlinux-51835949.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e61465cd524f/bzImage-51835949.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c6f3c081bf956c97e4de@syzkaller.appspotmail.com
Oops: divide error: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 PID: 11 Comm: kworker/u8:0 Not tainted 6.10.0-syzkaller-04472-g51835949dda3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:mac80211_hwsim_link_info_changed+0x409/0xf00 drivers/net/wireless/virtual/mac80211_hwsim.c:2547
Code: 00 fc ff df 43 80 7c 3d 00 00 48 8b 44 24 20 74 0f 48 8b 7c 24 20 e8 a6 ff 0d fb 48 8b 44 24 20 48 8b 08 89 ce 48 89 d8 31 d2 <48> f7 f6 29 d1 48 69 f1 e8 03 00 00 4c 89 f7 31 d2 b9 05 00 00 00
RSP: 0018:ffffc900001077a0 EFLAGS: 00010246
RAX: 00061d780b08a1f3 RBX: 00061d780b08a1f3 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000040
RBP: ffffc90000107890 R08: ffffffff8183f431 R09: 1ffffffff25f9ec5
R10: dffffc0000000000 R11: ffffffff813597f0 R12: 0000000000000200
R13: 1ffff1100c778e08 R14: ffff888063bc7048 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c34d35b CR3: 000000006a936000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
drv_link_info_changed+0x53d/0x8b0
ieee80211_offchannel_return+0x3a4/0x530 net/mac80211/offchannel.c:160
__ieee80211_scan_completed+0x77f/0xb60 net/mac80211/scan.c:495
ieee80211_scan_work+0x1cc/0x1da0 net/mac80211/scan.c:1162
cfg80211_wiphy_work+0x2db/0x490 net/wireless/core.c:440
process_one_work kernel/workqueue.c:3231 [inline]
process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312
worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:mac80211_hwsim_link_info_changed+0x409/0xf00 drivers/net/wireless/virtual/mac80211_hwsim.c:2547
Code: 00 fc ff df 43 80 7c 3d 00 00 48 8b 44 24 20 74 0f 48 8b 7c 24 20 e8 a6 ff 0d fb 48 8b 44 24 20 48 8b 08 89 ce 48 89 d8 31 d2 <48> f7 f6 29 d1 48 69 f1 e8 03 00 00 4c 89 f7 31 d2 b9 05 00 00 00
RSP: 0018:ffffc900001077a0 EFLAGS: 00010246
RAX: 00061d780b08a1f3 RBX: 00061d780b08a1f3 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000040
RBP: ffffc90000107890 R08: ffffffff8183f431 R09: 1ffffffff25f9ec5
R10: dffffc0000000000 R11: ffffffff813597f0 R12: 0000000000000200
R13: 1ffff1100c778e08 R14: ffff888063bc7048 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f37c5e6dfc8 CR3: 000000001f47a000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 3 bytes skipped:
0: df 43 80 filds -0x80(%rbx)
3: 7c 3d jl 0x42
5: 00 00 add %al,(%rax)
7: 48 8b 44 24 20 mov 0x20(%rsp),%rax
c: 74 0f je 0x1d
e: 48 8b 7c 24 20 mov 0x20(%rsp),%rdi
13: e8 a6 ff 0d fb call 0xfb0dffbe
18: 48 8b 44 24 20 mov 0x20(%rsp),%rax
1d: 48 8b 08 mov (%rax),%rcx
20: 89 ce mov %ecx,%esi
22: 48 89 d8 mov %rbx,%rax
25: 31 d2 xor %edx,%edx
* 27: 48 f7 f6 div %rsi <-- trapping instruction
2a: 29 d1 sub %edx,%ecx
2c: 48 69 f1 e8 03 00 00 imul $0x3e8,%rcx,%rsi
33: 4c 89 f7 mov %r14,%rdi
36: 31 d2 xor %edx,%edx
38: b9 05 00 00 00 mov $0x5,%ecx
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-07-18 8:46 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=000000000000152438061d819d0b@google.com \
--to=syzbot+c6f3c081bf956c97e4de@syzkaller.appspotmail.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®