From: Stanislav Fomichev <stfomichev@gmail.com>
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, andrew+netdev@lunn.ch,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
saeedm@nvidia.com, tariqt@nvidia.com, mbloch@nvidia.com,
alexanderduyck@fb.com, kernel-team@meta.com,
johannes@sipsolutions.net, sd@queasysnail.net,
jianbol@nvidia.com, dtatulea@nvidia.com, mohsin.bashr@gmail.com,
jacob.e.keller@intel.com, willemb@google.com,
skhawaja@google.com, bestswngs@gmail.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kselftest@vger.kernel.org,
leon@kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net-next v2 02/13] wifi: cfg80211: use __rtnl_unlock in nl80211_pre_doit
Date: Wed, 18 Mar 2026 09:16:24 -0700 [thread overview]
Message-ID: <abrP2NavLA4f5iHE@mini-arch> (raw)
In-Reply-To: <20260318150305.123900-3-sdf@fomichev.me>
On 03/18, Stanislav Fomichev wrote:
> nl80211_pre_doit acquires rtnl_lock and then wiphy_lock, releasing
> rtnl while keeping wiphy_lock held until post_doit. With the
> introduction of rx_mode_wq and its flush in netdev_run_todo, calling
> rtnl_unlock here creates a circular lock dependency:
>
> Chain exists of:
> (wq_completion)rx_mode_wq --> rtnl_mutex --> &rdev->wiphy.mtx
>
> Possible unsafe locking scenario:
>
> CPU0 CPU1
> ---- ----
> lock(&rdev->wiphy.mtx);
> lock(rtnl_mutex);
> lock(&rdev->wiphy.mtx);
> lock((wq_completion)rx_mode_wq);
>
> Switch to __rtnl_unlock to skip netdev_run_todo in nl80211_pre_doit.
> This seems safe because we run before the op.
>
> Link: http://lore.kernel.org/netdev/69b5ad67.a00a0220.3b25d1.001a.GAE@google.com
> Signed-off-by: Stanislav Fomichev <sdf@fomichev.me>
> ---
> net/wireless/nl80211.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
> index 2225f5d0b124..ce5f25d4c87e 100644
> --- a/net/wireless/nl80211.c
> +++ b/net/wireless/nl80211.c
> @@ -18192,7 +18192,7 @@ static int nl80211_pre_doit(const struct genl_split_ops *ops,
> __release(&rdev->wiphy.mtx);
> }
> if (!(internal_flags & NL80211_FLAG_NEED_RTNL))
> - rtnl_unlock();
> + __rtnl_unlock();
>
> return 0;
> out_unlock:
> --
> 2.53.0
>
ERROR: modpost: "__rtnl_unlock" [net/wireless/cfg80211.ko] undefined!
Gonna re-run local nipa ingest locally to see if anything else pops up.
---
pw-bot: cr
WARNING: multiple messages have this Message-ID (diff)
From: Stanislav Fomichev <stfomichev@gmail.com>
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, andrew+netdev@lunn.ch,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
saeedm@nvidia.com, tariqt@nvidia.com, mbloch@nvidia.com,
alexanderduyck@fb.com, kernel-team@meta.com,
johannes@sipsolutions.net, sd@queasysnail.net,
jianbol@nvidia.com, dtatulea@nvidia.com, mohsin.bashr@gmail.com,
jacob.e.keller@intel.com, willemb@google.com,
skhawaja@google.com, bestswngs@gmail.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kselftest@vger.kernel.org,
leon@kernel.org
Subject: Re: [PATCH net-next v2 02/13] wifi: cfg80211: use __rtnl_unlock in nl80211_pre_doit
Date: Wed, 18 Mar 2026 09:16:24 -0700 [thread overview]
Message-ID: <abrP2NavLA4f5iHE@mini-arch> (raw)
In-Reply-To: <20260318150305.123900-3-sdf@fomichev.me>
On 03/18, Stanislav Fomichev wrote:
> nl80211_pre_doit acquires rtnl_lock and then wiphy_lock, releasing
> rtnl while keeping wiphy_lock held until post_doit. With the
> introduction of rx_mode_wq and its flush in netdev_run_todo, calling
> rtnl_unlock here creates a circular lock dependency:
>
> Chain exists of:
> (wq_completion)rx_mode_wq --> rtnl_mutex --> &rdev->wiphy.mtx
>
> Possible unsafe locking scenario:
>
> CPU0 CPU1
> ---- ----
> lock(&rdev->wiphy.mtx);
> lock(rtnl_mutex);
> lock(&rdev->wiphy.mtx);
> lock((wq_completion)rx_mode_wq);
>
> Switch to __rtnl_unlock to skip netdev_run_todo in nl80211_pre_doit.
> This seems safe because we run before the op.
>
> Link: http://lore.kernel.org/netdev/69b5ad67.a00a0220.3b25d1.001a.GAE@google.com
> Signed-off-by: Stanislav Fomichev <sdf@fomichev.me>
> ---
> net/wireless/nl80211.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
> index 2225f5d0b124..ce5f25d4c87e 100644
> --- a/net/wireless/nl80211.c
> +++ b/net/wireless/nl80211.c
> @@ -18192,7 +18192,7 @@ static int nl80211_pre_doit(const struct genl_split_ops *ops,
> __release(&rdev->wiphy.mtx);
> }
> if (!(internal_flags & NL80211_FLAG_NEED_RTNL))
> - rtnl_unlock();
> + __rtnl_unlock();
>
> return 0;
> out_unlock:
> --
> 2.53.0
>
ERROR: modpost: "__rtnl_unlock" [net/wireless/cfg80211.ko] undefined!
Gonna re-run local nipa ingest locally to see if anything else pops up.
---
pw-bot: cr
next prev parent reply other threads:[~2026-03-18 16:16 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 15:02 [Intel-wired-lan] [PATCH net-next v2 00/13] net: sleepable ndo_set_rx_mode Stanislav Fomichev
2026-03-18 15:02 ` Stanislav Fomichev
2026-03-18 15:02 ` [Intel-wired-lan] [PATCH net-next v2 01/13] net: add address list snapshot and reconciliation infrastructure Stanislav Fomichev
2026-03-18 15:02 ` Stanislav Fomichev
2026-03-18 15:40 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-18 15:40 ` Loktionov, Aleksandr
2026-03-18 15:02 ` [Intel-wired-lan] [PATCH net-next v2 02/13] wifi: cfg80211: use __rtnl_unlock in nl80211_pre_doit Stanislav Fomichev
2026-03-18 15:02 ` Stanislav Fomichev
2026-03-18 15:41 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-18 15:41 ` Loktionov, Aleksandr
2026-03-18 16:16 ` Stanislav Fomichev [this message]
2026-03-18 16:16 ` Stanislav Fomichev
2026-03-19 9:16 ` [Intel-wired-lan] " kernel test robot
2026-03-19 19:22 ` kernel test robot
2026-03-18 15:02 ` [Intel-wired-lan] [PATCH net-next v2 03/13] net: introduce ndo_set_rx_mode_async and dev_rx_mode_work Stanislav Fomichev
2026-03-18 15:02 ` Stanislav Fomichev
2026-03-18 15:42 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-18 15:42 ` Loktionov, Aleksandr
2026-03-23 12:09 ` Loktionov, Aleksandr
2026-03-23 12:09 ` Loktionov, Aleksandr
2026-03-18 15:02 ` [Intel-wired-lan] [PATCH net-next v2 04/13] net: move promiscuity handling into dev_rx_mode_work Stanislav Fomichev
2026-03-18 15:02 ` Stanislav Fomichev
2026-03-18 15:43 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-18 15:43 ` Loktionov, Aleksandr
2026-03-18 15:02 ` [Intel-wired-lan] [PATCH net-next v2 05/13] fbnic: convert to ndo_set_rx_mode_async Stanislav Fomichev
2026-03-18 15:02 ` Stanislav Fomichev
2026-03-18 15:43 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-18 15:43 ` Loktionov, Aleksandr
2026-03-18 15:02 ` [Intel-wired-lan] [PATCH net-next v2 06/13] mlx5: " Stanislav Fomichev
2026-03-18 15:02 ` Stanislav Fomichev
2026-03-18 15:44 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-18 15:44 ` Loktionov, Aleksandr
2026-03-18 15:02 ` [Intel-wired-lan] [PATCH net-next v2 07/13] bnxt: " Stanislav Fomichev
2026-03-18 15:02 ` Stanislav Fomichev
2026-03-18 15:45 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-18 15:45 ` Loktionov, Aleksandr
2026-03-18 15:03 ` [Intel-wired-lan] [PATCH net-next v2 08/13] bnxt: use snapshot in bnxt_cfg_rx_mode Stanislav Fomichev
2026-03-18 15:03 ` Stanislav Fomichev
2026-03-19 8:31 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-03-19 8:31 ` Loktionov, Aleksandr
2026-03-19 15:54 ` Stanislav Fomichev
2026-03-18 15:03 ` [Intel-wired-lan] [PATCH net-next v2 09/13] iavf: convert to ndo_set_rx_mode_async Stanislav Fomichev
2026-03-18 15:03 ` Stanislav Fomichev
2026-03-18 15:03 ` [Intel-wired-lan] [PATCH net-next v2 10/13] netdevsim: " Stanislav Fomichev
2026-03-18 15:03 ` Stanislav Fomichev
2026-03-18 15:03 ` [Intel-wired-lan] [PATCH net-next v2 11/13] dummy: " Stanislav Fomichev
2026-03-18 15:03 ` Stanislav Fomichev
2026-03-18 15:03 ` [Intel-wired-lan] [PATCH net-next v2 12/13] net: warn ops-locked drivers still using ndo_set_rx_mode Stanislav Fomichev
2026-03-18 15:03 ` Stanislav Fomichev
2026-03-18 15:03 ` [Intel-wired-lan] [PATCH net-next v2 13/13] selftests: net: add team_bridge_macvlan rx_mode test Stanislav Fomichev
2026-03-18 15:03 ` Stanislav Fomichev
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=abrP2NavLA4f5iHE@mini-arch \
--to=stfomichev@gmail.com \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=bestswngs@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jianbol@nvidia.com \
--cc=johannes@sipsolutions.net \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=michael.chan@broadcom.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=saeedm@nvidia.com \
--cc=sd@queasysnail.net \
--cc=sdf@fomichev.me \
--cc=skhan@linuxfoundation.org \
--cc=skhawaja@google.com \
--cc=tariqt@nvidia.com \
--cc=willemb@google.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.