From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: bpf@vger.kernel.org, andrii@kernel.org, eddyz87@gmail.com,
ihor.solodrai@linux.dev, ast@kernel.org, daniel@iogearbox.net,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
shuah@kernel.org, chenyy23@mails.tsinghua.edu.cn,
puranjay@kernel.org, lorenzo@kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v1] selftests/bpf: Fix flaky bpf_nf test when random NAT port is 0
Date: Fri, 04 Sep 2026 17:00:05 +0000 [thread overview]
Message-ID: <178854120589.442795.9129340051112718540.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904073745.363314-1-jiayuan.chen@linux.dev>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 4 Sep 2026 15:37:39 +0800 you wrote:
> The bpf_nf test allocs a ct, sets snat and dnat with random addr and
> port via bpf_ct_set_nat_info(), then looks the ct up and checks the
> reply tuple against what was set.
>
> The port comes from bpf_get_prandom_u32() and can be 0. For
> bpf_ct_set_nat_info(), port 0 means "port not specified", so only the
> addr is mapped and the kernel keeps the original port. The check then
> compares that port with 0 and fails, which shows up as a flaky
> "Test for source natting" failure in CI [1][2].
>
> [...]
Here is the summary with links:
- [bpf-next,v1] selftests/bpf: Fix flaky bpf_nf test when random NAT port is 0
https://git.kernel.org/bpf/bpf/c/5e8c349bc8d7
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:[~2026-09-04 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 7:37 [PATCH bpf-next v1] selftests/bpf: Fix flaky bpf_nf test when random NAT port is 0 Jiayuan Chen
2026-09-04 17: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=178854120589.442795.9129340051112718540.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenyy23@mails.tsinghua.edu.cn \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jiayuan.chen@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=puranjay@kernel.org \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.