From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <kuba@kernel.org>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <horms@kernel.org>, <kuniyu@amazon.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>, <sdf@fomichev.me>
Subject: Re: [PATCH net-next] net: let lockdep compare instance locks
Date: Thu, 15 May 2025 18:49:07 -0700 [thread overview]
Message-ID: <20250516015114.40011-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250516012459.1385997-1-kuba@kernel.org>
From: Jakub Kicinski <kuba@kernel.org>
Date: Thu, 15 May 2025 18:24:59 -0700
> AFAIU always returning -1 from lockdep's compare function
> basically disables checking of dependencies between given
> locks. Try to be a little more precise about what guarantees
> that instance locks won't deadlock.
>
> Right now we only nest them under protection of rtnl_lock.
> Mostly in unregister_netdevice_many() and dev_close_many().
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> include/net/netdev_lock.h | 29 +++++++++++++++++++++--------
> 1 file changed, 21 insertions(+), 8 deletions(-)
>
> diff --git a/include/net/netdev_lock.h b/include/net/netdev_lock.h
> index 2a753813f849..75a2da23100d 100644
> --- a/include/net/netdev_lock.h
> +++ b/include/net/netdev_lock.h
> @@ -99,16 +99,29 @@ static inline void netdev_unlock_ops_compat(struct net_device *dev)
> static inline int netdev_lock_cmp_fn(const struct lockdep_map *a,
> const struct lockdep_map *b)
> {
> - /* Only lower devices currently grab the instance lock, so no
> - * real ordering issues can occur. In the near future, only
> - * hardware devices will grab instance lock which also does not
> - * involve any ordering. Suppress lockdep ordering warnings
> - * until (if) we start grabbing instance lock on pure SW
> - * devices (bond/team/veth/etc).
> - */
> +#ifdef CONFIG_DEBUG_NET_SMALL_RTNL
> + const struct net_device *dev_a, *dev_b;
> +
> + dev_a = container_of(a, struct net_device, lock.dep_map);
> + dev_b = container_of(b, struct net_device, lock.dep_map);
> +#endif
> +
> if (a == b)
> return 0;
> - return -1;
> +
> + /* Locking multiple devices usually happens under rtnl_lock */
> + if (lockdep_rtnl_is_held())
> + return -1;
> +
> +#ifdef CONFIG_DEBUG_NET_SMALL_RTNL
> + /* It's okay to use per-netns rtnl_lock if devices share netns */
> + if (net_eq(dev_net(dev_a), dev_net(dev_b)) &&
> + lockdep_rtnl_net_is_held(dev_net(dev_a)))
Do we need
!from_cleanup_net()
before lockdep_rtnl_net_is_held() ?
__rtnl_net_lock() is not held in ops_exit_rtnl_list() and
default_device_exit_batch() when calling unregister_netdevice_many().
> + return -1;
> +#endif
> +
> + /* Otherwise taking two instance locks is not allowed */
> + return 1;
> }
>
> #define netdev_lockdep_set_classes(dev) \
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-05-16 1:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 1:24 [PATCH net-next] net: let lockdep compare instance locks Jakub Kicinski
2025-05-16 1:49 ` Kuniyuki Iwashima [this message]
2025-05-16 2:36 ` Jakub Kicinski
2025-05-16 2:59 ` Kuniyuki Iwashima
2025-05-16 15:22 ` Jakub Kicinski
2025-05-16 17:14 ` Jakub Kicinski
2025-05-16 17:50 ` Kuniyuki Iwashima
2025-05-16 17:50 ` 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=20250516015114.40011-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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).