From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, edumazet@google.com
Subject: Re: [patch net-next v3 0/7] devlink: fix a deadlock when taking devlink instance lock while holding RTNL lock
Date: Wed, 18 Oct 2023 08:30:25 +0000 [thread overview]
Message-ID: <169761782525.24723.6762513832243789657.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231013121029.353351-1-jiri@resnulli.us>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 13 Oct 2023 14:10:22 +0200 you wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> devlink_port_fill() may be called sometimes with RTNL lock held.
> When putting the nested port function devlink instance attrs,
> current code takes nested devlink instance lock. In that case lock
> ordering is wrong.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/7] net: treat possible_net_t net pointer as an RCU one and add read_pnet_rcu()
https://git.kernel.org/netdev/net-next/c/2034d90ae41a
- [net-next,v3,2/7] devlink: call peernet2id_alloc() with net pointer under RCU read lock
https://git.kernel.org/netdev/net-next/c/c503bc7df602
- [net-next,v3,3/7] devlink: take device reference for devlink object
https://git.kernel.org/netdev/net-next/c/a380687200e0
- [net-next,v3,4/7] devlink: don't take instance lock for nested handle put
https://git.kernel.org/netdev/net-next/c/b5f4e371336a
- [net-next,v3,5/7] Documentation: devlink: add nested instance section
https://git.kernel.org/netdev/net-next/c/b6f23b319aad
- [net-next,v3,6/7] Documentation: devlink: add a note about RTNL lock into locking section
https://git.kernel.org/netdev/net-next/c/bb11cf9b2c4a
- [net-next,v3,7/7] devlink: document devlink_rel_nested_in_notify() function
https://git.kernel.org/netdev/net-next/c/5d77371e8c85
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-18 8:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 12:10 [patch net-next v3 0/7] devlink: fix a deadlock when taking devlink instance lock while holding RTNL lock Jiri Pirko
2023-10-13 12:10 ` [patch net-next v3 1/7] net: treat possible_net_t net pointer as an RCU one and add read_pnet_rcu() Jiri Pirko
2023-10-17 8:49 ` Simon Horman
2023-10-13 12:10 ` [patch net-next v3 2/7] devlink: call peernet2id_alloc() with net pointer under RCU read lock Jiri Pirko
2023-10-17 8:50 ` Simon Horman
2023-10-13 12:10 ` [patch net-next v3 3/7] devlink: take device reference for devlink object Jiri Pirko
2023-10-17 8:50 ` Simon Horman
2023-10-13 12:10 ` [patch net-next v3 4/7] devlink: don't take instance lock for nested handle put Jiri Pirko
2023-10-17 8:51 ` Simon Horman
2023-10-13 12:10 ` [patch net-next v3 5/7] Documentation: devlink: add nested instance section Jiri Pirko
2023-10-17 8:52 ` Simon Horman
2023-10-13 12:10 ` [patch net-next v3 6/7] Documentation: devlink: add a note about RTNL lock into locking section Jiri Pirko
2023-10-17 8:53 ` Simon Horman
2023-10-13 12:10 ` [patch net-next v3 7/7] devlink: document devlink_rel_nested_in_notify() function Jiri Pirko
2023-10-17 8:53 ` Simon Horman
2023-10-18 8:30 ` patchwork-bot+netdevbpf [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=169761782525.24723.6762513832243789657.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--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).