All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Eli Skeggs" <kernel@eliskeggs.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf 2/2] selftests/bpf: Redirect a bare FIN to another socket's egress
Date: Sun, 25 Oct 2026 23:55:07 +0000	[thread overview]
Message-ID: <sashiko-outbox-184525@kernel.org> (raw)
In-Reply-To: <20261025-sockmap-bare-fin-v1-2-bb8feae7c4a7@eliskeggs.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] selftests/bpf: non-standard multi-line comment style in sockmap_basic.c
--

commit 75aa8de4d43476db90b5d4bdecc71a03ce93e92c
Author: Eli Skeggs <kernel@eliskeggs.com>

selftests/bpf: Redirect a bare FIN to another socket's egress

This commit adds a sockmap selftest that redirects a bare FIN from a
half-closed socket to another socket's egress and verifies that data
subsequently redirected from a third socket still transmits without
setting an error on the destination socket.

> diff --git a/tools/testing/selftests/bpf/prog_tests/sockmap_basic.c b/tools/testing/selftests/bpf/prog_tests/sockmap_basic.c
> index 1fef6ec2ba7ae..e1e477ce72b32 100644
> --- a/tools/testing/selftests/bpf/prog_tests/sockmap_basic.c
> +++ b/tools/testing/selftests/bpf/prog_tests/sockmap_basic.c
> @@ -1325,6 +1325,78 @@ static void test_sockmap_multi_channels(int sotype)
>  	test_sockmap_pass_prog__destroy(skel);
>  }
>  
> +/* A bare FIN turns into an empty skb. When redirected to another socket,
> + * verify that it does not break the destination socket's psock. Data
> + * later redirected to the destination socket must still transmit.
> + */
> +static void test_sockmap_skb_verdict_redir_fin(void)

[Severity: Low]
This isn't a bug, but in tools/testing/selftests/bpf/prog_tests/sockmap_basic.c
above test_sockmap_skb_verdict_redir_fin(), the new multi-line comment places
text on the opening /* line. Could this follow the BPF subsystem multi-line
comment style by placing the opening /* on its own line:

/*
 * A bare FIN turns into an empty skb. When redirected to another socket,
 * verify that it does not break the destination socket's psock. Data
 * later redirected to the destination socket must still transmit.
 */

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261025-sockmap-bare-fin-v1-0-bb8feae7c4a7@eliskeggs.com?part=2

  reply	other threads:[~2026-10-25 23:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25 23:41 [PATCH bpf 0/2] bpf, sockmap: Fix dropped data and EPIPE on empty skb redirect Eli Skeggs
2026-10-25 23:41 ` Eli Skeggs via B4 Relay
2026-10-25 23:41 ` [PATCH bpf 1/2] bpf, sockmap: Stop reporting EPIPE on zero-length " Eli Skeggs
2026-10-25 23:41   ` Eli Skeggs via B4 Relay
2026-10-26  1:51   ` Alexei Starovoitov
2026-10-26  2:25     ` Eli Skeggs
2026-10-26  1:59   ` Jiayuan Chen
2026-10-26  3:17     ` Eli Skeggs
2026-10-26  6:32       ` Jiayuan Chen
2026-10-25 23:41 ` [PATCH bpf 2/2] selftests/bpf: Redirect a bare FIN to another socket's egress Eli Skeggs
2026-10-25 23:41   ` Eli Skeggs via B4 Relay
2026-10-25 23:55   ` sashiko-bot [this message]
2026-10-26  0:28     ` Eli Skeggs

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=sashiko-outbox-184525@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=kernel@eliskeggs.com \
    --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 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.