From: Mahe Tardy <mahe.tardy@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v7 4/7] selftests/bpf: add bpf_icmp_send kfunc cgroup_skb tests
Date: Wed, 27 May 2026 00:06:58 +0200 [thread overview]
Message-ID: <ahYZgpQR452LBeP-@gmail.com> (raw)
In-Reply-To: <20260526192443.843F11F000E9@smtp.kernel.org>
On Tue, May 26, 2026 at 07:24:43PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] Multi-line comment does not follow the required BPF subsystem style.
> --
>
> commit 67ff0f6d65a210627d2fdadf8ec80c32d95d6a59
> Author: Mahe Tardy <mahe.tardy@gmail.com>
>
> selftests/bpf: add bpf_icmp_send kfunc cgroup_skb tests
>
> This commit adds a test for the bpf_icmp_send kfunc using a cgroup_skb
> egress program. It verifies that ICMP unreach messages are correctly sent
> back to the client and read from the socket's error queue.
>
> > diff --git a/tools/testing/selftests/bpf/prog_tests/icmp_send_kfunc.c b/tools/testing/selftests/bpf/prog_tests/icmp_send_kfunc.c
> > new file mode 100644
> > index 0000000000000..0dc6b6ceafb4a
> > --- /dev/null
> > +++ b/tools/testing/selftests/bpf/prog_tests/icmp_send_kfunc.c
>
> [ ... ]
>
> > @@ -126,10 +126,10 @@ void test_icmp_send_unreach_cgroup(void)
> > + for (int code = 0; code <= NR_ICMP_UNREACH; code++) {
> > + /* The TCP stack reacts differently when asking for
> > + * fragmentation, let's ignore it for now.
> > + */
>
> [Severity: Low]
> This isn't a bug, but does this multi-line comment follow the preferred
> kernel comment style for the BPF subsystem? The style guidelines require
> the opening /* to be on its own line.
Could fix this small style issue if required.
>
> > + if (code == ICMP_FRAG_NEEDED)
> > + continue;
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260526153708.279717-1-mahe.tardy@gmail.com?part=4
next prev parent reply other threads:[~2026-05-26 22:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 15:37 [PATCH bpf-next v7 0/7] bpf: add icmp_send kfunc Mahe Tardy
2026-05-26 15:37 ` [PATCH bpf-next v7 1/7] net: move netfilter nf_reject_fill_skb_dst to core ipv4 Mahe Tardy
2026-05-26 16:20 ` bot+bpf-ci
2026-05-28 22:54 ` Jordan Rife
2026-05-26 15:37 ` [PATCH bpf-next v7 2/7] net: move netfilter nf_reject6_fill_skb_dst to core ipv6 Mahe Tardy
2026-05-26 16:20 ` bot+bpf-ci
2026-05-26 22:02 ` Mahe Tardy
2026-05-28 22:55 ` Jordan Rife
2026-05-26 15:37 ` [PATCH bpf-next v7 3/7] bpf: add bpf_icmp_send kfunc Mahe Tardy
2026-05-28 22:55 ` Jordan Rife
2026-05-29 9:02 ` Mahe Tardy
2026-05-29 16:33 ` Jordan Rife
2026-05-29 16:38 ` Jordan Rife
2026-05-26 15:37 ` [PATCH bpf-next v7 4/7] selftests/bpf: add bpf_icmp_send kfunc cgroup_skb tests Mahe Tardy
2026-05-26 16:20 ` bot+bpf-ci
2026-05-26 19:24 ` sashiko-bot
2026-05-26 22:06 ` Mahe Tardy [this message]
2026-05-29 16:38 ` Jordan Rife
2026-05-26 15:37 ` [PATCH bpf-next v7 5/7] selftests/bpf: add bpf_icmp_send kfunc cgroup_skb IPv6 tests Mahe Tardy
2026-05-26 19:32 ` sashiko-bot
2026-05-26 22:07 ` Mahe Tardy
2026-05-26 15:37 ` [PATCH bpf-next v7 6/7] selftests/bpf: add bpf_icmp_send kfunc tc tests Mahe Tardy
2026-05-26 15:37 ` [PATCH bpf-next v7 7/7] selftests/bpf: add bpf_icmp_send recursion test Mahe Tardy
2026-05-26 20:22 ` sashiko-bot
2026-05-26 22:10 ` Mahe Tardy
2026-05-28 22:55 ` Jordan Rife
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=ahYZgpQR452LBeP-@gmail.com \
--to=mahe.tardy@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=sashiko-reviews@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox