From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, netdev@vger.kernel.org, hawk@kernel.org,
M202472210@hust.edu.cn, dddddd@hust.edu.cn
Subject: Re: [PATCH bpf-next 1/2] bpf: Check skb->transport_header is set in bpf_skb_check_mtu
Date: Sat, 15 Nov 2025 02:50:07 +0000 [thread overview]
Message-ID: <176317500727.1918140.1454108210011393739.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251112232331.1566074-1-martin.lau@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 12 Nov 2025 15:23:30 -0800 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
>
> The bpf_skb_check_mtu helper needs to use skb->transport_header when
> the BPF_MTU_CHK_SEGS flag is used:
>
> bpf_skb_check_mtu(skb, ifindex, &mtu_len, 0, BPF_MTU_CHK_SEGS)
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Check skb->transport_header is set in bpf_skb_check_mtu
https://git.kernel.org/bpf/bpf-next/c/d946f3c98328
- [bpf-next,2/2] selftests/bpf: Test bpf_skb_check_mtu(BPF_MTU_CHK_SEGS) when transport_header is not set
https://git.kernel.org/bpf/bpf-next/c/6cc73f35406c
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-11-15 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 23:23 [PATCH bpf-next 1/2] bpf: Check skb->transport_header is set in bpf_skb_check_mtu Martin KaFai Lau
2025-11-12 23:23 ` [PATCH bpf-next 2/2] selftests/bpf: Test bpf_skb_check_mtu(BPF_MTU_CHK_SEGS) when transport_header is not set Martin KaFai Lau
2025-11-15 2:50 ` 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=176317500727.1918140.1454108210011393739.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=M202472210@hust.edu.cn \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dddddd@hust.edu.cn \
--cc=hawk@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
/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