From: patchwork-bot+netdevbpf@kernel.org
To: Antoine Tenart <atenart@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, dsahern@kernel.org,
netdev@vger.kernel.org, ssuryaextr@gmail.com, pabeni@redhat.com
Subject: Re: [PATCH net] vrf: do not push non-ND strict packets with a source LLA through packet taps again
Date: Mon, 21 Jun 2021 19:00:03 +0000 [thread overview]
Message-ID: <162430200368.28611.1289742615939222752.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210618151553.59456-1-atenart@kernel.org>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 18 Jun 2021 17:15:53 +0200 you wrote:
> Non-ND strict packets with a source LLA go through the packet taps
> again, while non-ND strict packets with other source addresses do not,
> and we can see a clone of those packets on the vrf interface (we should
> not). This is due to a series of changes:
>
> Commit 6f12fa775530[1] made non-ND strict packets not being pushed again
> in the packet taps. This changed with commit 205704c618af[2] for those
> packets having a source LLA, as they need a lookup with the orig_iif.
>
> [...]
Here is the summary with links:
- [net] vrf: do not push non-ND strict packets with a source LLA through packet taps again
https://git.kernel.org/netdev/net/c/603113c514e9
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:[~2021-06-21 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 15:15 [PATCH net] vrf: do not push non-ND strict packets with a source LLA through packet taps again Antoine Tenart
2021-06-19 1:18 ` David Ahern
2021-06-20 12:12 ` Antoine Tenart
2021-06-21 3:20 ` David Ahern
2021-06-21 19:00 ` 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=162430200368.28611.1289742615939222752.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ssuryaextr@gmail.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).