From: syzbot <syzbot+4ef359e6b423499fa4e1@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] WARNING: lock held when returning to user space in ieee80211_change_mac
Date: Sat, 01 Oct 2022 07:26:40 -0700 [thread overview]
Message-ID: <0000000000001850d105e9f9e6de@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 6627a2074d5c net/smc: Support SO_REUSEPORT
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10183a70880000
kernel config: https://syzkaller.appspot.com/x/.config?x=d4d64087513b5aa1
dashboard link: https://syzkaller.appspot.com/bug?extid=4ef359e6b423499fa4e1
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9ecb75606956/disk-6627a207.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1073865fcb40/vmlinux-6627a207.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4ef359e6b423499fa4e1@syzkaller.appspotmail.com
================================================
WARNING: lock held when returning to user space!
6.0.0-rc6-syzkaller-01407-g6627a2074d5c #0 Not tainted
------------------------------------------------
syz-executor.3/10164 is leaving the kernel with locks still held!
1 lock held by syz-executor.3/10164:
#0: ffff888147acaa88 (&local->mtx){+.+.}-{3:3}, at: ieee80211_can_powered_addr_change net/mac80211/iface.c:217 [inline]
#0: ffff888147acaa88 (&local->mtx){+.+.}-{3:3}, at: ieee80211_change_mac+0x9b4/0xf40 net/mac80211/iface.c:264
---
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:[~2022-10-01 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 14:26 syzbot [this message]
2022-10-02 20:02 ` [syzbot] WARNING: lock held when returning to user space in ieee80211_change_mac Johannes Berg
2022-10-03 8:00 ` Dmitry Vyukov
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=0000000000001850d105e9f9e6de@google.com \
--to=syzbot+4ef359e6b423499fa4e1@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.