From: syzbot <syzbot+d7aa450b9ba2a184513b@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com,
johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [wireless?] WARNING in ieee80211_do_stop (2)
Date: Thu, 11 Jul 2024 09:32:19 -0700 [thread overview]
Message-ID: <0000000000007c77b5061cfb4ec6@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 2f5e6395714d Merge branch 'net-pse-pd-add-new-pse-c33-feat..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17f48376980000
kernel config: https://syzkaller.appspot.com/x/.config?x=db697e01efa9d1d7
dashboard link: https://syzkaller.appspot.com/bug?extid=d7aa450b9ba2a184513b
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/44296878e8d6/disk-2f5e6395.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a3f8523e4843/vmlinux-2f5e6395.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c40a60a2869f/bzImage-2f5e6395.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d7aa450b9ba2a184513b@syzkaller.appspotmail.com
netdevsim netdevsim1 netdevsim2: entered allmulticast mode
netdevsim netdevsim1 netdevsim3: entered promiscuous mode
netdevsim netdevsim1 netdevsim3: entered allmulticast mode
mac80211_hwsim hwsim10 wlan0: entered promiscuous mode
mac80211_hwsim hwsim10 wlan0: entered allmulticast mode
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7335 at net/mac80211/iface.c:515 ieee80211_do_stop+0x18ee/0x1ee0 net/mac80211/iface.c:515
Modules linked in:
CPU: 0 PID: 7335 Comm: syz.1.716 Not tainted 6.10.0-rc6-syzkaller-01258-g2f5e6395714d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
RIP: 0010:ieee80211_do_stop+0x18ee/0x1ee0 net/mac80211/iface.c:515
Code: ff e8 a6 32 9c f6 4c 89 ef 31 f6 e8 1c 4c 0c 00 48 8b 5c 24 60 e9 9d fd ff ff e8 8d 32 9c f6 e9 93 fd ff ff e8 83 32 9c f6 90 <0f> 0b 90 e9 cd ea ff ff e8 75 32 9c f6 90 43 0f b6 04 27 84 c0 0f
RSP: 0018:ffffc9000d726800 EFLAGS: 00010246
RAX: ffffffff8af9f4dd RBX: 0000000000000002 RCX: 0000000000040000
RDX: ffffc900093ec000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffc9000d726968 R08: ffffffff8af9dfa0 R09: 1ffffffff1f5b9ad
R10: dffffc0000000000 R11: fffffbfff1f5b9ae R12: dffffc0000000000
R13: ffff88807a598e20 R14: 0000000000000001 R15: ffff88807a8a2800
FS: 00007f0f44fb46c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f53c3a15fa3 CR3: 0000000069780000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_stop+0x436/0x4a0 net/mac80211/iface.c:761
__dev_close_many+0x219/0x300 net/core/dev.c:1558
__dev_close net/core/dev.c:1570 [inline]
__dev_change_flags+0x30e/0x6f0 net/core/dev.c:8835
dev_change_flags+0x8b/0x1a0 net/core/dev.c:8909
do_setlink+0xccd/0x41f0 net/core/rtnetlink.c:2900
rtnl_group_changelink net/core/rtnetlink.c:3447 [inline]
__rtnl_newlink net/core/rtnetlink.c:3706 [inline]
rtnl_newlink+0x1119/0x20a0 net/core/rtnetlink.c:3743
rtnetlink_rcv_msg+0x89b/0x1180 net/core/rtnetlink.c:6641
netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2550
netlink_unicast_kernel net/netlink/af_netlink.c:1331 [inline]
netlink_unicast+0x7f0/0x990 net/netlink/af_netlink.c:1357
netlink_sendmsg+0x8e4/0xcb0 net/netlink/af_netlink.c:1901
sock_sendmsg_nosec net/socket.c:730 [inline]
__sock_sendmsg+0x221/0x270 net/socket.c:745
____sys_sendmsg+0x525/0x7d0 net/socket.c:2585
___sys_sendmsg net/socket.c:2639 [inline]
__sys_sendmsg+0x2b0/0x3a0 net/socket.c:2668
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0f44175bd9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0f44fb4048 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f0f44303f60 RCX: 00007f0f44175bd9
RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000000000005
RBP: 00007f0f441e4aa1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f0f44303f60 R15: 00007ffe2ab3ef88
</TASK>
---
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-11 16:32 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=0000000000007c77b5061cfb4ec6@google.com \
--to=syzbot+d7aa450b9ba2a184513b@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=pabeni@redhat.com \
--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.