From: David Ahern <dsahern@kernel.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v2 2/4] ipv6: fix source address selection with route leak
Date: Sun, 7 Jul 2024 10:58:49 -0600 [thread overview]
Message-ID: <35638894-254f-4e30-98ee-5a3d6886d87a@kernel.org> (raw)
In-Reply-To: <20240705145302.1717632-3-nicolas.dichtel@6wind.com>
On 7/5/24 8:52 AM, Nicolas Dichtel wrote:
> diff --git a/include/net/ip6_route.h b/include/net/ip6_route.h
> index a18ed24fed94..a7c27f0c6bce 100644
> --- a/include/net/ip6_route.h
> +++ b/include/net/ip6_route.h
> @@ -127,18 +127,23 @@ void rt6_age_exceptions(struct fib6_info *f6i, struct fib6_gc_args *gc_args,
>
> static inline int ip6_route_get_saddr(struct net *net, struct fib6_info *f6i,
> const struct in6_addr *daddr,
> - unsigned int prefs,
> + unsigned int prefs, int l3mdev_index,
> struct in6_addr *saddr)
> {
> + struct net_device *l3mdev;
> + struct net_device *dev;
> + bool same_vrf;
> int err = 0;
>
> - if (f6i && f6i->fib6_prefsrc.plen) {
> + rcu_read_lock();
> + l3mdev = dev_get_by_index_rcu(net, l3mdev_index);
> + dev = f6i ? fib6_info_nh_dev(f6i) : NULL;
> + same_vrf = l3mdev == NULL || l3mdev_master_dev_rcu(dev) == l3mdev;
!l3mdev; checkpatch should complain
> + if (f6i && f6i->fib6_prefsrc.plen && same_vrf)
> *saddr = f6i->fib6_prefsrc.addr;
> - } else {
> - struct net_device *dev = f6i ? fib6_info_nh_dev(f6i) : NULL;
> -
> - err = ipv6_dev_get_saddr(net, dev, daddr, prefs, saddr);
> - }
> + else
> + err = ipv6_dev_get_saddr(net, same_vrf ? dev : l3mdev, daddr, prefs, saddr);
> + rcu_read_unlock();
>
> return err;
> }
lot of logic lines jammed together. put a new line after the read_lock()
and before the unlock().
next prev parent reply other threads:[~2024-07-07 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240705145302.1717632-1-nicolas.dichtel@6wind.com>
2024-07-05 14:52 ` [PATCH net v2 1/4] ipv4: fix source address selection with route leak Nicolas Dichtel
2024-07-07 16:58 ` David Ahern
2024-07-08 18:13 ` Nicolas Dichtel
2024-07-08 20:32 ` Jakub Kicinski
2024-07-08 21:27 ` Nicolas Dichtel
2024-07-05 14:52 ` [PATCH net v2 2/4] ipv6: " Nicolas Dichtel
2024-07-07 16:58 ` David Ahern [this message]
2024-07-08 18:15 ` Nicolas Dichtel
2024-07-08 18:44 ` David Ahern
2024-07-08 21:24 ` Nicolas Dichtel
2024-07-05 14:52 ` [PATCH net v2 3/4] ipv6: take care of scope when choosing the src addr Nicolas Dichtel
2024-07-07 17:00 ` David Ahern
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=35638894-254f-4e30-98ee-5a3d6886d87a@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
/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