From: patchwork-bot+netdevbpf@kernel.org
To: Philo Lu <lulie@linux.alibaba.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
asml.silence@gmail.com, willemb@google.com,
almasrymina@google.com, chopps@labn.net,
aleksander.lobakin@intel.com, nicolas.dichtel@6wind.com,
dust.li@linux.alibaba.com, hustcat@gmail.com, ja@ssi.bg,
horms@verge.net.au, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 net] ipvs: Always clear ipvs_property flag in skb_scrub_packet()
Date: Tue, 25 Feb 2025 12:30:32 +0000 [thread overview]
Message-ID: <174048663224.4155054.13422794267665315194.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250222033518.126087-1-lulie@linux.alibaba.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 22 Feb 2025 11:35:18 +0800 you wrote:
> We found an issue when using bpf_redirect with ipvs NAT mode after
> commit ff70202b2d1a ("dev_forward_skb: do not scrub skb mark within
> the same name space"). Particularly, we use bpf_redirect to return
> the skb directly back to the netif it comes from, i.e., xnet is
> false in skb_scrub_packet(), and then ipvs_property is preserved
> and SNAT is skipped in the rx path.
>
> [...]
Here is the summary with links:
- [PATCHv2,net] ipvs: Always clear ipvs_property flag in skb_scrub_packet()
https://git.kernel.org/netdev/net/c/de2c211868b9
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:[~2025-02-25 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 3:35 Philo Lu
2025-02-25 10:55 ` Julian Anastasov
2025-02-25 12:30 ` 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=174048663224.4155054.13422794267665315194.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=almasrymina@google.com \
--cc=asml.silence@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=chopps@labn.net \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=horms@verge.net.au \
--cc=hustcat@gmail.com \
--cc=ja@ssi.bg \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lulie@linux.alibaba.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=willemb@google.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
all inboxes | Powered by JetHome®