From: Johannes Berg <johannes@sipsolutions.net>
To: Zhao Li <enderaoelyther@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Javier Lopez <jlopex@gmail.com>,
Jukka Rissanen <jukka.rissanen@linux.intel.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 2/2] wifi: mac80211_hwsim: serialize radio removal with frame commands
Date: Tue, 10 Nov 2026 11:54:21 +0100 [thread overview]
Message-ID: <76bc126fb977cac0f0a124fc80eae9fdb803264d.camel@sipsolutions.net> (raw)
In-Reply-To: <20261028141751.6728-3-enderaoelyther@gmail.com> (sfid-20261028_151822_083722_A5EF7A18)
On Wed, 2026-10-28 at 22:17 +0800, Zhao Li wrote:
> Destroying a radio while a frame, TX status, or PMSR command is in
> progress can make the command access the radio after it has been freed.
>
> DEFINE_SPINLOCK(hwsim_radio_lock);
> +static DEFINE_MUTEX(hwsim_radio_mutex);
That, with significant work done under the mutex, seems like too big a
hammer, can't it really not be done in any other way?
johannes
next prev parent reply other threads:[~2026-11-10 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 14:17 [PATCH 0/2] wifi: mac80211_hwsim: fix netlink release and radio removal races Zhao Li
2026-10-28 14:17 ` [PATCH 1/2] wifi: mac80211_hwsim: ignore non-generic netlink releases Zhao Li
2026-10-28 14:17 ` [PATCH 2/2] wifi: mac80211_hwsim: serialize radio removal with frame commands Zhao Li
2026-11-10 10:54 ` Johannes Berg [this message]
2026-10-29 8:38 ` [syzbot ci] Re: wifi: mac80211_hwsim: fix netlink release and radio removal races syzbot ci
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=76bc126fb977cac0f0a124fc80eae9fdb803264d.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=enderaoelyther@gmail.com \
--cc=jlopex@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®