From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <pabeni@redhat.com>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <horms@kernel.org>, <kuba@kernel.org>,
<kuni1840@gmail.com>, <kuniyu@amazon.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH RESEND v2 net-next 02/14] ipv6: Get rid of RTNL for SIOCDELRT and RTM_DELROUTE.
Date: Wed, 16 Apr 2025 11:45:57 -0700 [thread overview]
Message-ID: <20250416184559.99881-1-kuniyu@amazon.com> (raw)
In-Reply-To: <3e28015e-0ca0-4933-80b5-de45e3c43b11@redhat.com>
From: Paolo Abeni <pabeni@redhat.com>
Date: Wed, 16 Apr 2025 10:49:53 +0200
> On 4/14/25 8:14 PM, Kuniyuki Iwashima wrote:
> > Basically, removing an IPv6 route does not require RTNL because
> > the IPv6 routing tables are protected by per table lock.
> >
> > inet6_rtm_delroute() calls nexthop_find_by_id() to check if the
> > nexthop specified by RTA_NH_ID exists. nexthop uses rbtree and
> > the top-down walk can be safely performed under RCU.
> >
> > ip6_route_del() already relies on RCU and the table lock, but we
> > need to extend the RCU critical section a bit more to cover
> > __ip6_del_rt(). For example, nexthop_for_each_fib6_nh() and
> > inet6_rt_notify() needs RCU.
>
> The last statement is not clear to me. I don't see __ip6_del_rt()
> calling nexthop_for_each_fib6_nh() or inet6_rt_notify() ?!?
Thank you for review!
It's burried in the depths, and I noticed this from the v1 test result.
https://lore.kernel.org/netdev/Z91yk90LZy9yJexG@mini-arch/
inet6_rtm_delroute
ip6_route_del
__ip6_del_rt
fib6_del
fib6_del_route
fib6_purge_rt
nexthop_for_each_fib6_nh
inet6_rtm_delroute
ip6_route_del
__ip6_del_rt
fib6_del
fib6_del_route
inet6_rt_notify
>
> Also after this patch we have this chunk in ip6_route_del():
>
> table = fib6_get_table(cfg->fc_nlinfo.nl_net, cfg->fc_table);
> if (!table)
> //..
>
> rcu_read_lock();
>
> which AFAICS should be safe because 'table' is freed only at netns exit
> time,
Right, and there are few other functions assuming the same thing.
addrconf_get_prefix_route()
rt6_get_route_info()
> but acquiring the rcu lock after grabbing the rcu protected struct
> is confusing. It should be good adding a comment or moving the rcu lock
> before the lookup (and dropping the RCU lock from fib6_get_table())
There are other callers of fib6_get_table(), so I'd move rcu_read_lock()
before it, and will look into them if we can drop it from fib6_get_table().
next prev parent reply other threads:[~2025-04-16 18:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 18:14 [PATCH RESEND v2 net-next 00/14] ipv6: No RTNL for IPv6 routing table Kuniyuki Iwashima
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 01/14] ipv6: Validate RTA_GATEWAY of RTA_MULTIPATH in rtm_to_fib6_config() Kuniyuki Iwashima
2025-04-16 8:22 ` Paolo Abeni
2025-04-17 17:53 ` Kuniyuki Iwashima
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 02/14] ipv6: Get rid of RTNL for SIOCDELRT and RTM_DELROUTE Kuniyuki Iwashima
2025-04-16 8:49 ` Paolo Abeni
2025-04-16 18:45 ` Kuniyuki Iwashima [this message]
2025-04-17 6:46 ` Paolo Abeni
2025-04-17 17:45 ` Kuniyuki Iwashima
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 03/14] ipv6: Move some validation from ip6_route_info_create() to rtm_to_fib6_config() Kuniyuki Iwashima
2025-04-16 8:54 ` Paolo Abeni
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 04/14] ipv6: Check GATEWAY in rtm_to_fib6_multipath_config() Kuniyuki Iwashima
2025-04-16 9:06 ` Paolo Abeni
2025-04-16 18:48 ` Kuniyuki Iwashima
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 05/14] ipv6: Move nexthop_find_by_id() after fib6_info_alloc() Kuniyuki Iwashima
2025-04-16 9:13 ` Paolo Abeni
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 06/14] ipv6: Split ip6_route_info_create() Kuniyuki Iwashima
2025-04-16 9:12 ` Paolo Abeni
2025-04-16 18:50 ` Kuniyuki Iwashima
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 07/14] ipv6: Preallocate rt->fib6_nh->rt6i_pcpu in ip6_route_info_create() Kuniyuki Iwashima
2025-04-16 9:21 ` Paolo Abeni
2025-04-16 9:37 ` Paolo Abeni
2025-04-16 18:55 ` Kuniyuki Iwashima
2025-04-16 9:23 ` Paolo Abeni
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 08/14] ipv6: Preallocate nhc_pcpu_rth_output " Kuniyuki Iwashima
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 09/14] ipv6: Don't pass net to ip6_route_info_append() Kuniyuki Iwashima
2025-04-16 9:39 ` Paolo Abeni
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 10/14] ipv6: Factorise ip6_route_multipath_add() Kuniyuki Iwashima
2025-04-16 9:57 ` Paolo Abeni
2025-04-16 18:58 ` Kuniyuki Iwashima
2025-04-14 18:14 ` [PATCH RESEND v2 net-next 11/14] ipv6: Protect fib6_link_table() with spinlock Kuniyuki Iwashima
2025-04-16 10:00 ` Paolo Abeni
2025-04-14 18:15 ` [PATCH RESEND v2 net-next 12/14] ipv6: Defer fib6_purge_rt() in fib6_add_rt2node() to fib6_add() Kuniyuki Iwashima
2025-04-16 13:59 ` Paolo Abeni
2025-04-14 18:15 ` [PATCH RESEND v2 net-next 13/14] ipv6: Protect nh->f6i_list with spinlock and flag Kuniyuki Iwashima
2025-04-16 15:17 ` Paolo Abeni
2025-04-16 19:02 ` Kuniyuki Iwashima
2025-04-14 18:15 ` [PATCH RESEND v2 net-next 14/14] ipv6: Get rid of RTNL for SIOCADDRT and RTM_NEWROUTE Kuniyuki Iwashima
2025-04-16 15:26 ` Paolo Abeni
2025-04-16 19:04 ` Kuniyuki Iwashima
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=20250416184559.99881-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--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).