From: Philo Lu <lulie@linux.alibaba.com>
To: Julian Anastasov <ja@ssi.bg>
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,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] ipvs: Always clear ipvs_property flag in skb_scrub_packet()
Date: Fri, 21 Feb 2025 19:55:27 +0800 [thread overview]
Message-ID: <365859bd-1457-4f83-91f4-34a7f21e1d8f@linux.alibaba.com> (raw)
In-Reply-To: <610b255c-51e4-0460-05a2-ab9cd8c43295@ssi.bg>
On 2025/2/21 19:42, Julian Anastasov wrote:
>
> Hello,
>
> On Fri, 21 Feb 2025, Philo Lu 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.
>>
>> ipvs_property has been already cleared when netns is changed in
>> commit 2b5ec1a5f973 ("netfilter/ipvs: clear ipvs_property flag when
>> SKB net namespace changed"). This patch just clears it in spite of
>> netns.
>>
>> Signed-off-by: Philo Lu <lulie@linux.alibaba.com>
>> ---
>> This is in fact a fix patch, and the issue was found after commit
>> ff70202b2d1a ("dev_forward_skb: do not scrub skb mark within
>> the same name space"). But I'm not sure if a "Fixes" tag should be
>> added to that commit.
>
> You can add 2b5ec1a5f973 as a Fixes tag in v2 and I'll ack it.
Thank you, Julian. You also solve my worries. I'll post v2 soon.
--
Philo
prev parent reply other threads:[~2025-02-21 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 1:36 Philo Lu
2025-02-21 10:13 ` Nicolas Dichtel
2025-02-21 15:59 ` Julian Anastasov
2025-02-21 11:42 ` Julian Anastasov
2025-02-21 11:55 ` Philo Lu [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=365859bd-1457-4f83-91f4-34a7f21e1d8f@linux.alibaba.com \
--to=lulie@linux.alibaba.com \
--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=hustcat@gmail.com \
--cc=ja@ssi.bg \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®