From: Mahe Tardy <mahe.tardy@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v6 5/6] selftests/bpf: add bpf_icmp_send kfunc IPv6 tests
Date: Mon, 18 May 2026 20:13:25 +0200 [thread overview]
Message-ID: <agtWxQedLwq1X-Rq@gmail.com> (raw)
In-Reply-To: <20260518164538.21D3BC2BCB7@smtp.kernel.org>
On Mon, May 18, 2026 at 04:45:37PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] Buffer truncation and type mismatch when calling getsockname() for IPv6 sockets.
> --
>
> commit 324aeb5b326896da717647e51a1e69a4c3e6f647
> Author: Mahe Tardy <mahe.tardy@gmail.com>
>
> selftests/bpf: add bpf_icmp_send kfunc IPv6 tests
>
> This commit extends the existing ICMP send tests with IPv6 support.
>
> > diff --git a/tools/testing/selftests/bpf/prog_tests/icmp_send_kfunc.c b/tools/testing/selftests/bpf/prog_tests/icmp_send_kfunc.c
> > --- a/tools/testing/selftests/bpf/prog_tests/icmp_send_kfunc.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/icmp_send_kfunc.c
> > @@ -81,14 +95,13 @@ static void read_icmp_errqueue(int sockfd, int expected_code)
> > }
> >
> > static void trigger_prog_read_icmp_errqueue(struct icmp_send *skel,
> > - int code)
> > + int code, int af, const char *ip)
> > {
> > int srv_fd = -1, client_fd = -1;
> > struct sockaddr_in addr;
> > socklen_t len = sizeof(addr);
> >
> > - srv_fd = start_server(AF_INET, SOCK_STREAM, "127.0.0.1", 0,
> > - TIMEOUT_MS);
> > + srv_fd = start_server(af, SOCK_STREAM, ip, 0, TIMEOUT_MS);
> > if (!ASSERT_GE(srv_fd, 0, "start_server"))
> > return;
> >
> > if (getsockname(srv_fd, (struct sockaddr *)&addr, &len)) {
> > close(srv_fd);
> > return;
> > }
> > skel->bss->server_port = ntohs(addr.sin_port);
>
> Since start_server() can now return an IPv6 socket, does getsockname() truncate
> the 28-byte IPv6 address data into the 16-byte sockaddr_in structure here?
>
> Should addr be updated to a struct sockaddr_storage to safely handle both
> address families, along with a cast to read the port properly?
Duplicate bot review, do we care for reading the port? I don't think
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260518122842.218522-1-mahe.tardy@gmail.com?part=5
next prev parent reply other threads:[~2026-05-18 18:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 12:28 [PATCH bpf-next v6 0/4] bpf: add icmp_send kfunc Mahe Tardy
2026-05-18 12:28 ` [PATCH bpf-next v6 1/6] net: move netfilter nf_reject_fill_skb_dst to core ipv4 Mahe Tardy
2026-05-18 13:07 ` bot+bpf-ci
2026-05-18 14:21 ` Mahe Tardy
2026-05-18 12:28 ` [PATCH bpf-next v6 2/6] net: move netfilter nf_reject6_fill_skb_dst to core ipv6 Mahe Tardy
2026-05-18 13:07 ` bot+bpf-ci
2026-05-18 14:22 ` Mahe Tardy
2026-05-18 12:28 ` [PATCH bpf-next v6 3/6] bpf: add bpf_icmp_send kfunc Mahe Tardy
2026-05-18 13:34 ` bot+bpf-ci
2026-05-18 14:26 ` Mahe Tardy
2026-05-18 16:17 ` Stanislav Fomichev
2026-05-18 17:18 ` Mahe Tardy
2026-05-19 21:20 ` Stanislav Fomichev
2026-05-18 16:25 ` sashiko-bot
2026-05-19 1:33 ` Jordan Rife
2026-05-20 18:48 ` Mahe Tardy
2026-05-18 12:28 ` [PATCH bpf-next v6 4/6] selftests/bpf: add bpf_icmp_send kfunc tests Mahe Tardy
2026-05-19 1:34 ` Jordan Rife
2026-05-20 19:15 ` Mahe Tardy
2026-05-18 12:28 ` [PATCH bpf-next v6 5/6] selftests/bpf: add bpf_icmp_send kfunc IPv6 tests Mahe Tardy
2026-05-18 13:21 ` bot+bpf-ci
2026-05-18 14:27 ` Mahe Tardy
2026-05-18 16:45 ` sashiko-bot
2026-05-18 18:13 ` Mahe Tardy [this message]
2026-05-18 12:28 ` [PATCH bpf-next v6 6/6] selftests/bpf: add bpf_icmp_send recursion test Mahe Tardy
2026-05-18 13:07 ` bot+bpf-ci
2026-05-18 14:39 ` Mahe Tardy
2026-05-18 17:07 ` sashiko-bot
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=agtWxQedLwq1X-Rq@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 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.