From: syzbot <syzbot+8dcc087eb24227ded47e@syzkaller.appspotmail.com>
To: davem@davemloft.net, johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: WARNING in sta_info_insert_check
Date: Sun, 31 Jan 2021 21:26:23 -0800 [thread overview]
Message-ID: <00000000000037b29b05ba3f9859@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: bec4c296 Merge tag 'ecryptfs-5.11-rc6-setxattr-fix' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11991778d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f75d66d6d359ef2f
dashboard link: https://syzkaller.appspot.com/bug?extid=8dcc087eb24227ded47e
userspace arch: arm64
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+8dcc087eb24227ded47e@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 118 at net/mac80211/sta_info.c:547 sta_info_insert_check+0x48/0xc4 net/mac80211/sta_info.c:547
Modules linked in:
CPU: 0 PID: 118 Comm: kworker/u4:3 Not tainted 5.11.0-rc5-syzkaller-00239-gbec4c2968fce #0
Hardware name: linux,dummy-virt (DT)
Workqueue: phy6 ieee80211_iface_work
pstate: 40400009 (nZcv daif +PAN -UAO -TCO BTYPE=--)
pc : sta_info_insert_check+0x48/0xc4 net/mac80211/sta_info.c:547
lr : sta_info_insert_rcu+0x34/0x90 net/mac80211/sta_info.c:725
sp : ffff800013f3bbf0
x29: ffff800013f3bbf0 x28: ffff8000132e4538
x27: f6ff00002070c998 x26: dead000000000100
x25: dead000000000122 x24: f6ff00002070d340
x23: f6ff00002070d280 x22: faff000020710800
x21: faff000020710df0 x20: f6ff00002070c940
x19: f7ff000020784000 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000
x15: 0000ad1062c19046 x14: f7ff000020796098
x13: 000000000000044b x12: f6ff00002070c940
x11: 000000000000000c x10: 0000000000000000
x9 : faff000020713b90 x8 : 0000000000000fff
x7 : 0000000000000000 x6 : f6ff00002070c940
x5 : 0000000000000fff x4 : 0000000000000000
x3 : 0000000000000100 x2 : 00000000ffeeffff
x1 : 00000000ffffffff x0 : 00000000ffeefdf7
Call trace:
sta_info_insert_check+0x48/0xc4 net/mac80211/sta_info.c:547
sta_info_insert_rcu+0x34/0x90 net/mac80211/sta_info.c:725
ieee80211_ibss_finish_sta+0x84/0x140 net/mac80211/ibss.c:592
ieee80211_ibss_work+0xe4/0x560 net/mac80211/ibss.c:1700
ieee80211_iface_work+0x2b8/0x33c net/mac80211/iface.c:1445
process_one_work+0x1d8/0x360 kernel/workqueue.c:2275
worker_thread+0x74/0x440 kernel/workqueue.c:2421
kthread+0x178/0x180 kernel/kthread.c:292
ret_from_fork+0x10/0x30 arch/arm64/kernel/entry.S:958
---
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.
next reply other threads:[~2021-02-01 5:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 5:26 syzbot [this message]
2021-02-01 9:12 ` WARNING in sta_info_insert_check Johannes Berg
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=00000000000037b29b05ba3f9859@google.com \
--to=syzbot+8dcc087eb24227ded47e@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--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=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;
as well as URLs for NNTP newsgroup(s).