[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000000000001850d105e9f9e6de@google.com>
Date: Sat, 01 Oct 2022 07:26:40 -0700
From: syzbot <syzbot+4ef359e6b423499fa4e1@...kaller.appspotmail.com>
To: davem@...emloft.net, edumazet@...gle.com,
johannes@...solutions.net, kuba@...nel.org,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
netdev@...r.kernel.org, pabeni@...hat.com,
syzkaller-bugs@...glegroups.com
Subject: [syzbot] WARNING: lock held when returning to user space in ieee80211_change_mac
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@...kaller.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@...glegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
Powered by blists - more mailing lists