From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <kuba@kernel.org>
Cc: <davem@davemloft.net>, <dsahern@gmail.com>, <edumazet@google.com>,
<jiri@resnulli.us>, <netdev@vger.kernel.org>, <pabeni@redhat.com>,
<kuniyu@amazon.com>
Subject: Re: [PATCH net-next 1/2] rtnetlink: move rtnl_lock handling out of af_netlink
Date: Thu, 6 Jun 2024 16:33:03 -0700 [thread overview]
Message-ID: <20240606233303.37245-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20240606192906.1941189-2-kuba@kernel.org>
From: Jakub Kicinski <kuba@kernel.org>
Date: Thu, 6 Jun 2024 12:29:05 -0700
> Now that we have an intermediate layer of code for handling
> rtnl-level netlink dump quirks, we can move the rtnl_lock
> taking there.
>
> For dump handlers with RTNL_FLAG_DUMP_SPLIT_NLM_DONE we can
> avoid taking rtnl_lock just to generate NLM_DONE, once again.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> net/core/rtnetlink.c | 9 +++++++--
> net/netlink/af_netlink.c | 2 --
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c
> index 4668d6718040..eabfc8290f5e 100644
> --- a/net/core/rtnetlink.c
> +++ b/net/core/rtnetlink.c
> @@ -6486,6 +6486,7 @@ static int rtnl_mdb_del(struct sk_buff *skb, struct nlmsghdr *nlh,
>
> static int rtnl_dumpit(struct sk_buff *skb, struct netlink_callback *cb)
> {
> + const bool needs_lock = !(cb->flags & RTNL_FLAG_DUMP_UNLOCKED);
> rtnl_dumpit_func dumpit = cb->data;
> int err;
>
> @@ -6495,7 +6496,11 @@ static int rtnl_dumpit(struct sk_buff *skb, struct netlink_callback *cb)
> if (!dumpit)
> return 0;
>
> + if (needs_lock)
> + rtnl_lock();
> err = dumpit(skb, cb);
> + if (needs_lock)
> + rtnl_unlock();
This calls netdev_run_todo() now, is this change intended ?
Other parts look good to me.
>
> /* Old dump handlers used to send NLM_DONE as in a separate recvmsg().
> * Some applications which parse netlink manually depend on this.
> @@ -6515,7 +6520,8 @@ static int rtnetlink_dump_start(struct sock *ssk, struct sk_buff *skb,
> const struct nlmsghdr *nlh,
> struct netlink_dump_control *control)
> {
> - if (control->flags & RTNL_FLAG_DUMP_SPLIT_NLM_DONE) {
> + if (control->flags & RTNL_FLAG_DUMP_SPLIT_NLM_DONE ||
> + !(control->flags & RTNL_FLAG_DUMP_UNLOCKED)) {
> WARN_ON(control->data);
> control->data = control->dump;
> control->dump = rtnl_dumpit;
> @@ -6703,7 +6709,6 @@ static int __net_init rtnetlink_net_init(struct net *net)
> struct netlink_kernel_cfg cfg = {
> .groups = RTNLGRP_MAX,
> .input = rtnetlink_rcv,
> - .cb_mutex = &rtnl_mutex,
> .flags = NL_CFG_F_NONROOT_RECV,
> .bind = rtnetlink_bind,
> };
> diff --git a/net/netlink/af_netlink.c b/net/netlink/af_netlink.c
> index fa9c090cf629..8bbbe75e75db 100644
> --- a/net/netlink/af_netlink.c
> +++ b/net/netlink/af_netlink.c
> @@ -2330,8 +2330,6 @@ static int netlink_dump(struct sock *sk, bool lock_taken)
>
> cb->extack = &extack;
>
> - if (cb->flags & RTNL_FLAG_DUMP_UNLOCKED)
> - extra_mutex = NULL;
> if (extra_mutex)
> mutex_lock(extra_mutex);
> nlk->dump_done_errno = cb->dump(skb, cb);
> --
> 2.45.2
next prev parent reply other threads:[~2024-06-06 23:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 19:29 [PATCH net-next 0/2] rtnetlink: move rtnl_lock handling out of af_netlink Jakub Kicinski
2024-06-06 19:29 ` [PATCH net-next 1/2] " Jakub Kicinski
2024-06-06 23:33 ` Kuniyuki Iwashima [this message]
2024-06-07 0:04 ` Jakub Kicinski
2024-06-07 0:18 ` Kuniyuki Iwashima
2024-06-07 9:24 ` Eric Dumazet
2024-06-06 19:29 ` [PATCH net-next 2/2] net: netlink: remove the cb_mutex "injection" from netlink core Jakub Kicinski
2024-06-06 23:35 ` Kuniyuki Iwashima
2024-06-06 22:31 ` [PATCH net-next 0/2] rtnetlink: move rtnl_lock handling out of af_netlink David Ahern
2024-06-10 12:20 ` patchwork-bot+netdevbpf
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=20240606233303.37245-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--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).