[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202510141649.D0DDA6A57@keescook>
Date: Tue, 14 Oct 2025 16:56:44 -0700
From: Kees Cook <kees@...nel.org>
To: bot+bpf-ci@...nel.org
Cc: kernel-ci@...a.com, andrii@...nel.org, daniel@...earbox.net,
martin.lau@...ux.dev, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2 00/10] net: Introduce struct sockaddr_unspec
On Tue, Oct 14, 2025 at 11:06:58PM +0000, bot+bpf-ci@...nel.org wrote:
> Dear patch submitter,
>
> CI has tested the following submission:
> Status: FAILURE
> Name: [v2,00/10] net: Introduce struct sockaddr_unspec
> Patchwork: https://patchwork.kernel.org/project/netdevbpf/list/?series=1011557&state=*
> Matrix: https://github.com/kernel-patches/bpf/actions/runs/18512305054
Hrm, there's something in here that wasn't caught with my "allmodconfig"
tests. I'll take a closer look...
Ah, yes. I missed these:
tools/testing/selftests/bpf/prog_tests/sock_addr.c:static int kernel_bind(int fd, struct sockaddr *addr, socklen_t addrlen)
tools/testing/selftests/bpf/prog_tests/sock_addr.c: if (kernel_bind(0, (struct sockaddr *)&addr, addrlen) < 0)
tools/testing/selftests/bpf/test_kmods/bpf_testmod.c: err = kernel_bind(sock, (struct sockaddr *)&args->addr, args->addrlen);
etc...
I will get those fixed.
--
Kees Cook
Powered by blists - more mailing lists