[v6.1] WARNING in drv_link_info_changed

0 views
Skip to first unread message

syzbot

unread,
Apr 10, 2023, 1:52:46 AM4/10/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16a2b44bc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9ccbc3d5467efd1
dashboard link: https://syzkaller.appspot.com/bug?extid=eb1582764c752a7bf324
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7fe538fc87bf/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8df93997601a/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/03ad7e3bf859/Image-543aff19.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+eb1582...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5842 at net/mac80211/driver-ops.c:423 drv_link_info_changed+0x230/0x70c
Modules linked in:
CPU: 1 PID: 5842 Comm: kworker/u4:18 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: phy6 ieee80211_roc_work
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : drv_link_info_changed+0x230/0x70c
lr : drv_link_info_changed+0x230/0x70c
sp : ffff800023787980
x29: ffff800023787980 x28: 1fffe00025251cff x27: dfff800000000000
x26: 0000000000001b00 x25: ffff00012928e7f8 x24: 0000000000000000
x23: ffff00012928cc80 x22: 0000000080000000 x21: ffff00012928e7d8
x20: 0000000000000200 x19: ffff0000c1ef8e00 x18: 1fffe000368bab76
x17: ffff80001557d000 x16: ffff8000084f40fc x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000005 x12: ffff000125651b40
x11: ff8080001195919c x10: 0000000000000000 x9 : ffff80001195919c
x8 : ffff000125651b40 x7 : ffff800011988d08 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000200 x3 : 0000000000000000
x2 : 0000000000000000 x1 : ffff800017d905c0 x0 : 0000000080000000
Call trace:
drv_link_info_changed+0x230/0x70c
ieee80211_link_info_change_notify+0x138/0x1f8 net/mac80211/main.c:290
ieee80211_offchannel_stop_vifs+0x200/0x484 net/mac80211/offchannel.c:121
_ieee80211_start_next_roc+0x524/0x97c net/mac80211/offchannel.c:365
__ieee80211_roc_work+0x1bc/0x2bc net/mac80211/offchannel.c:432
ieee80211_roc_work+0x38/0x50 net/mac80211/offchannel.c:460
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289
worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
irq event stamp: 4490322
hardirqs last enabled at (4490321): [<ffff8000121b9b0c>] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
hardirqs last enabled at (4490321): [<ffff8000121b9b0c>] _raw_spin_unlock_irqrestore+0x48/0xac kernel/locking/spinlock.c:194
hardirqs last disabled at (4490322): [<ffff8000120d75ac>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (4490294): [<ffff8000119a8a04>] spin_unlock_bh include/linux/spinlock.h:395 [inline]
softirqs last enabled at (4490294): [<ffff8000119a8a04>] ieee80211_ibss_work+0x2d8/0x1230 net/mac80211/ibss.c:1701
softirqs last disabled at (4490292): [<ffff8000119a8804>] spin_lock_bh include/linux/spinlock.h:355 [inline]
softirqs last disabled at (4490292): [<ffff8000119a8804>] ieee80211_ibss_work+0xd8/0x1230 net/mac80211/ibss.c:1690
---[ end trace 0000000000000000 ]---
wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50
wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50


---
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,
Aug 8, 2023, 1:52:42 AM8/8/23
to syzkaller...@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