public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ricardo B. Marlière" <rbm@suse.com>
To: "Harshit Mogalapalli" <harshit.m.mogalapalli@oracle.com>,
	"Shung-Hsi Yu" <shung-hsi.yu@suse.com>, <stable@vger.kernel.org>
Cc: "Ricardo B. Marlière" <rbm@suse.com>
Subject: Re: [PATCH stable 6.12 0/5] Backport selftest for "bpf: Check skb->transport_header is set in bpf_skb_check_mtu"
Date: Tue, 24 Feb 2026 09:18:04 -0300	[thread overview]
Message-ID: <DGN6PFT94YHU.3S3UXTP82975E@suse.com> (raw)
In-Reply-To: <bd0277b7-4a19-46a4-9f06-96d48cbc89d8@oracle.com>

On Tue Feb 24, 2026 at 4:53 AM -03, Harshit Mogalapalli wrote:
> Hi,
>
> On 24/02/26 13:08, Shung-Hsi Yu wrote:
>> This patchset backport the corresponding BPF selftests for commit
>> d946f3c98328 ("bpf: Check skb->transport_header is set in
>> bpf_skb_check_mtu"), which has already been included since 6.12.63.
>> 
>> The BPF selftest added in commit 6cc73f35406c ("selftests/bpf: Test
>> bpf_skb_check_mtu(BPF_MTU_CHK_SEGS) when transport_header is not set")
>> additionally depends on network namespace support for BPF selftests
>> added by Bastien, otherwise the MTU in root networking namespace will be
>> set to 10, causing other BPF selftests to fail. Credit goes to Ricardo
>> Marlière for figuring out the dependency.
>> 
>
> Note:
> I have recently learnt that ideally we are supposed to run upstream 
> latest kselftests on stable kernels as well. If a feature is not 
> supported the kselftests are meant to be skipped.

That is not true for BPF, from my (limited) experience.

>
> https://lore.kernel.org/all/a45eaddb-9e17-4e82-8a78-a1d1f6e3d735@linuxfoundation.org/
>
> Thanks,
> Harshit
>> Bastien Curutchet (eBPF Foundation) (4):
>>    selftests/bpf: ns_current_pid_tgid: Rename the test function
>>    selftests/bpf: Optionally open a dedicated namespace to run test in it
>>    selftests/bpf: tc_links/tc_opts: Unserialize tests
>>    selftests/bpf: ns_current_pid_tgid: Use test_progs's ns_ feature
>> 
>> Martin KaFai Lau (1):
>>    selftests/bpf: Test bpf_skb_check_mtu(BPF_MTU_CHK_SEGS) when
>>      transport_header is not set
>> 
>>   .../selftests/bpf/prog_tests/check_mtu.c      | 23 ++++++++-
>>   .../bpf/prog_tests/ns_current_pid_tgid.c      | 49 +++++++------------
>>   .../selftests/bpf/prog_tests/tc_links.c       | 28 +++++------
>>   .../selftests/bpf/prog_tests/tc_opts.c        | 40 +++++++--------
>>   .../selftests/bpf/progs/test_check_mtu.c      | 12 +++++
>>   tools/testing/selftests/bpf/test_progs.c      | 12 +++++
>>   6 files changed, 98 insertions(+), 66 deletions(-)
>> 


  reply	other threads:[~2026-02-24 12:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24  7:38 [PATCH stable 6.12 0/5] Backport selftest for "bpf: Check skb->transport_header is set in bpf_skb_check_mtu" Shung-Hsi Yu
2026-02-24  7:38 ` [PATCH stable 6.12 1/5] selftests/bpf: ns_current_pid_tgid: Rename the test function Shung-Hsi Yu
2026-02-24  7:38 ` [PATCH stable 6.12 2/5] selftests/bpf: Optionally open a dedicated namespace to run test in it Shung-Hsi Yu
2026-02-24  7:38 ` [PATCH stable 6.12 3/5] selftests/bpf: tc_links/tc_opts: Unserialize tests Shung-Hsi Yu
2026-02-24  7:38 ` [PATCH stable 6.12 4/5] selftests/bpf: ns_current_pid_tgid: Use test_progs's ns_ feature Shung-Hsi Yu
2026-02-24  7:38 ` [PATCH stable 6.12 5/5] selftests/bpf: Test bpf_skb_check_mtu(BPF_MTU_CHK_SEGS) when transport_header is not set Shung-Hsi Yu
2026-02-24  7:53 ` [PATCH stable 6.12 0/5] Backport selftest for "bpf: Check skb->transport_header is set in bpf_skb_check_mtu" Harshit Mogalapalli
2026-02-24 12:18   ` Ricardo B. Marlière [this message]
2026-02-25  2:35     ` Latest BPF selftests on stable kernels (was 'Re: [PATCH stable 6.12 0/5] Backport selftest for "bpf: Check skb->transport_header is set in bpf_skb_check_mtu"') Shung-Hsi Yu
2026-02-25 14:32       ` Greg KH
2026-02-26  7:33         ` Shung-Hsi Yu

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=DGN6PFT94YHU.3S3UXTP82975E@suse.com \
    --to=rbm@suse.com \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=shung-hsi.yu@suse.com \
    --cc=stable@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