From: Johannes Berg <johannes@sipsolutions.net>
To: syzbot <syzbot+70ce058e01259de7bb1d@syzkaller.appspotmail.com>,
kvalo@codeaurora.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
Benjamin Beichler <benjamin.beichler@uni-rostock.de>
Subject: Re: KASAN: use-after-free Read in mac80211_hwsim_del_radio
Date: Thu, 01 Mar 2018 10:30:38 +0100 [thread overview]
Message-ID: <1519896638.2292.7.camel@sipsolutions.net> (raw)
In-Reply-To: <001a113ecf342db684056655e097@google.com> (sfid-20180301_094507_144777_9C69AA6F)
Hi,
> syzbot hit the following crash on upstream commit
> f3afe530d644488a074291da04a69a296ab63046 (Tue Feb 27 22:02:39 2018 +0000)
> Merge branch 'fixes-v4.16-rc4' of
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security
>
> So far this crash happened 4 times on upstream.
> Unfortunately, I don't have any reproducer for this crash yet.
> Raw console output is attached.
That's ... a pretty complex scenario.
Looks like we have a race between destroying a network namespace, which
moves everything back into the init_ns and may have to rename objects
asynchronously (cleanup_net), with destroying the radio in hwsim that's
also asynchronous (destroy_radio).
Benjamin, would you be able to take a look at this? I'm preparing for a
trip and will leave Saturday for a week so I don't think I'll be able
to really dig into this before mid-March.
johannes
next parent reply other threads:[~2018-03-01 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a113ecf342db684056655e097@google.com>
2018-03-01 9:30 ` Johannes Berg [this message]
2018-03-01 12:32 ` KASAN: use-after-free Read in mac80211_hwsim_del_radio Benjamin Beichler
2018-03-01 12:35 ` Johannes Berg
2018-03-01 17:48 ` Benjamin Beichler
2018-03-01 12:55 ` Kirill Tkhai
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=1519896638.2292.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benjamin.beichler@uni-rostock.de \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+70ce058e01259de7bb1d@syzkaller.appspotmail.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 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).