From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <kuba@kernel.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <horms@kernel.org>,
<kuni1840@gmail.com>, <kuniyu@amazon.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>
Subject: Re: [PATCH v1 net-next 0/4] net: Hold per-netns RTNL during netdev notifier registration.
Date: Sun, 5 Jan 2025 16:59:57 +0900 [thread overview]
Message-ID: <20250105075957.67334-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250104073740.597af5c0@kernel.org>
From: Jakub Kicinski <kuba@kernel.org>
Date: Sat, 4 Jan 2025 07:37:40 -0800
> On Sat, 4 Jan 2025 15:37:31 +0900 Kuniyuki Iwashima wrote:
> > Patch 1 converts the global netdev notifier to blocking_notifier,
> > which will be called under per-netns RTNL without RTNL, then we
> > need to protect the ongoing netdev_chain users from unregistration.
> >
> > Patch 2 ~ 4 adds per-netns RTNL for registration of the global
> > and per-netns netdev notifiers.
>
> Lockdep is not happy:
>
> [ 249.261403][ T11] ============================================
> [ 249.261592][ T11] WARNING: possible recursive locking detected
> [ 249.261769][ T11] 6.13.0-rc5-virtme #1 Not tainted
> [ 249.261920][ T11] --------------------------------------------
> [ 249.262094][ T11] kworker/u16:0/11 is trying to acquire lock:
> [ 249.262293][ T11] ffffffff8a7f6a70 ((netdev_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x50/0x90
> [ 249.262591][ T11]
> [ 249.262591][ T11] but task is already holding lock:
> [ 249.262810][ T11] ffffffff8a7f6a70 ((netdev_chain).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x50/0x90
> [ 249.263100][ T11]
> [ 249.263100][ T11] other info that might help us debug this:
> [ 249.263310][ T11] Possible unsafe locking scenario:
> [ 249.263310][ T11]
> [ 249.263522][ T11] CPU0
> [ 249.263624][ T11] ----
> [ 249.263728][ T11] lock((netdev_chain).rwsem);
> [ 249.263875][ T11] lock((netdev_chain).rwsem);
Ah, lockdep annotaion was needed for the nested notifier calls.
But this will not be a meaningful annotation and needs to be changed
once rtnl_setlink/dellink supports per-netns RTNL.
I'll drop patch 1 and just leave a comment around RTNL in
register_netdevice_notifier() in patch 2.
Another option would be clone each netdev notifier during registration
and unshare(2)/clone(2) and force notifiers to be namespacified ?
---8<---
diff --git a/net/core/dev.c b/net/core/dev.c
index a0dd34463901..8bf8d565f42d 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -446,6 +446,17 @@ static void unlist_netdevice(struct net_device *dev)
static BLOCKING_NOTIFIER_HEAD(netdev_chain);
+#ifdef CONFIG_PROVE_LOCKING
+static int netdev_chain_lock_cmp_fn(const struct lockdep_map *a,
+ const struct lockdep_map *b)
+{
+ if (rtnl_is_locked())
+ return -1;
+
+ return 1;
+}
+#endif
+
/*
* Device drivers call our routines to queue packets here. We empty the
* queue in the local softnet handler.
@@ -12229,6 +12240,8 @@ static int __init net_dev_init(void)
net_dev_struct_check();
+ lock_set_cmp_fn(&netdev_chain.rwsem, netdev_chain_lock_cmp_fn, NULL);
+
if (dev_proc_init())
goto out;
---8<---
prev parent reply other threads:[~2025-01-05 8:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 6:37 [PATCH v1 net-next 0/4] net: Hold per-netns RTNL during netdev notifier registration Kuniyuki Iwashima
2025-01-04 6:37 ` [PATCH v1 net-next 1/4] net: Convert netdev_chain to blocking_notifier Kuniyuki Iwashima
2025-01-08 2:28 ` kernel test robot
2025-01-04 6:37 ` [PATCH v1 net-next 2/4] net: Hold __rtnl_net_lock() in (un)?register_netdevice_notifier() Kuniyuki Iwashima
2025-01-04 6:37 ` [PATCH v1 net-next 3/4] net: Hold rtnl_net_lock() in (un)?register_netdevice_notifier_net() Kuniyuki Iwashima
2025-01-04 6:37 ` [PATCH v1 net-next 4/4] net: Hold rtnl_net_lock() in (un)?register_netdevice_notifier_dev_net() Kuniyuki Iwashima
2025-01-15 22:16 ` Yael Chemla
2025-01-16 2:54 ` Kuniyuki Iwashima
2025-01-20 18:55 ` Yael Chemla
2025-01-27 17:26 ` Yael Chemla
2025-01-27 17:54 ` Kuniyuki Iwashima
2025-01-27 23:26 ` Kuniyuki Iwashima
2025-01-29 16:21 ` Yael Chemla
2025-01-30 0:32 ` Kuniyuki Iwashima
2025-01-04 15:37 ` [PATCH v1 net-next 0/4] net: Hold per-netns RTNL during netdev notifier registration Jakub Kicinski
2025-01-05 7:59 ` Kuniyuki Iwashima [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=20250105075957.67334-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).