Netdev List
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: Antoine Tenart <atenart@kernel.org>,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com
Cc: netdev@vger.kernel.org, Jianlin Shi <jishi@redhat.com>
Subject: Re: [PATCH net] net: vrf: determine the dst using the original ifindex for multicast
Date: Tue, 20 Dec 2022 11:58:26 -0700	[thread overview]
Message-ID: <5fc56e61-487f-96e8-5b39-c64f891eb334@kernel.org> (raw)
In-Reply-To: <20221220171825.1172237-1-atenart@kernel.org>

On 12/20/22 10:18 AM, Antoine Tenart wrote:
> Multicast packets received on an interface bound to a VRF are marked as
> belonging to the VRF and the skb device is updated to point to the VRF
> device itself. This was fine even when a route was associated to a
> device as when performing a fib table lookup 'oif' in fib6_table_lookup
> (coming from 'skb->dev->ifindex' in ip6_route_input) was set to 0 when
> FLOWI_FLAG_SKIP_NH_OIF was set.
> 
> With commit 40867d74c374 ("net: Add l3mdev index to flow struct and
> avoid oif reset for port devices") this is not longer true and multicast
> traffic is not received on the original interface.
> 
> Instead of adding back a similar check in fib6_table_lookup determine
> the dst using the original ifindex for multicast VRF traffic. To make
> things consistent across the function do the above for all strict
> packets, which was the logic before commit 6f12fa775530 ("vrf: mark skb
> for multicast or link-local as enslaved to VRF"). Note that reverting to
> this behavior should be fine as the change was about marking packets
> belonging to the VRF, not about their dst.
> 
> Fixes: 40867d74c374 ("net: Add l3mdev index to flow struct and avoid oif reset for port devices")
> Cc: David Ahern <dsahern@kernel.org>
> Reported-by: Jianlin Shi <jishi@redhat.com>
> Signed-off-by: Antoine Tenart <atenart@kernel.org>
> ---
>  drivers/net/vrf.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 

Reviewed-by: David Ahern <dsahern@kernel.org>



  reply	other threads:[~2022-12-20 18:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 17:18 [PATCH net] net: vrf: determine the dst using the original ifindex for multicast Antoine Tenart
2022-12-20 18:58 ` David Ahern [this message]
2022-12-22  1:50 ` 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=5fc56e61-487f-96e8-5b39-c64f891eb334@kernel.org \
    --to=dsahern@kernel.org \
    --cc=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jishi@redhat.com \
    --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