From: Johannes Berg <johannes@sipsolutions.net>
To: Cosmin Ratiu <cratiu@nvidia.com>, linux-wireless@vger.kernel.org
Cc: Tariq Toukan <tariqt@nvidia.com>,
Carolina Jubran <cjubran@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] wifi: wext: Limit notifier event flushes to the device's netns
Date: Wed, 21 Oct 2026 17:21:46 +0200 [thread overview]
Message-ID: <8a508046f36d8f483137ab6715722318af2b147d.camel@sipsolutions.net> (raw)
In-Reply-To: <20261021144111.611840-1-cratiu@nvidia.com>
On Wed, 2026-10-21 at 17:41 +0300, Cosmin Ratiu wrote:
> With mlx5 netdev instance locking enabled, registering an IPoIB netdev
> calls the WEXT notifier while holding the instance mutex.
I hate wext :)
> It may seem strange that the fix for a lock cycle across multiple
> subsystems lies in a completely unrelated part of the code, but this
> seemed the most justified lock cycle edge to break.
Yeah, seems fair. Finally a good reason for my ~17 year old commit to
have the wext events per netns? Today I'd probably have rejected it as
useless churn ;-)
LGTM.
johannes
prev parent reply other threads:[~2026-10-21 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 14:41 [PATCH] wifi: wext: Limit notifier event flushes to the device's netns Cosmin Ratiu
2026-10-21 14:57 ` Cosmin Ratiu
2026-10-21 15:21 ` Johannes Berg [this message]
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=8a508046f36d8f483137ab6715722318af2b147d.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=dtatulea@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tariqt@nvidia.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