netdev - Re: [PATCH bpf v1 1/2] bpf: cpumap: propagate underlying error in cpu_map_update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251206122711.62868-1-enjuk@amazon.com>
Date: Sat, 6 Dec 2025 21:26:51 +0900
From: Kohei Enju <enjuk@...zon.com>
To: <alexei.starovoitov@...il.com>
CC: <andrii@...nel.org>, <ast@...nel.org>, <bpf@...r.kernel.org>,
	<daniel@...earbox.net>, <davem@...emloft.net>, <eddyz87@...il.com>,
	<enjuk@...zon.com>, <haoluo@...gle.com>, <hawk@...nel.org>,
	<john.fastabend@...il.com>, <jolsa@...nel.org>, <kernel-team@...udflare.com>,
	<kohei.enju@...il.com>, <kpsingh@...nel.org>, <kuba@...nel.org>,
	<lorenzo@...nel.org>, <martin.lau@...ux.dev>, <netdev@...r.kernel.org>,
	<sdf@...ichev.me>, <shuah@...nel.org>, <song@...nel.org>, <toke@...nel.org>,
	<yonghong.song@...ux.dev>
Subject: Re: [PATCH bpf v1 1/2] bpf: cpumap: propagate underlying error in cpu_map_update_elem()

On Sat, 6 Dec 2025 04:22:02 -0800, Alexei Starovoitov wrote:

>On Sat, Dec 6, 2025 at 9:14 PM Kohei Enju <enjuk@...zon.com> wrote:
>>
>> On Sat, 6 Dec 2025 04:06:38 -0800, Alexei Starovoitov wrote:
>>
>> >On Sat, Dec 6, 2025 at 9:01 PM Kohei Enju <enjuk@...zon.com> wrote:
>> >>
>> >> Ah, I forgot that bpf-next is closed until Jan 2nd due to the merge window.
>> >> I'll resend v2 after Jan 2nd :)
>> >
>> >?! It's not closed. net-next is.
>>
>> Oh, really?
>> Hmm, I've read the documentation[1], but I may misunderstand something. Perhaps that documentation is outdated?
>>
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/bpf/bpf_devel_QA.rst#n232
>
>yes. It's seriously outdated. bpf-next was never closed.

Today I learned! Thank you for the clarification.

As originally planned, I will work on v2 next week :)