From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Chris Mason <clm@meta.com>, Leon Hwang <leon.hwang@linux.dev>,
bot+bpf-ci@kernel.org, bpf@vger.kernel.org
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
jolsa@kernel.org, yonghong.song@linux.dev, song@kernel.org,
eddyz87@gmail.com, dxu@dxuuu.xyz, deso@posteo.net,
martin.lau@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
shuah@kernel.org, kerneljasonxing@gmail.com,
chen.dylane@linux.dev, willemb@google.com,
paul.chaignon@gmail.com, a.s.protopopov@gmail.com,
memxor@gmail.com, yatsenko@meta.com, tklauser@distanz.ch,
kernel-patches-bot@fb.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v12 2/7] bpf: Add BPF_F_CPU and BPF_F_ALL_CPUS flags support for percpu_array maps
Date: Wed, 26 Nov 2025 14:20:06 -0800 [thread overview]
Message-ID: <68ecc660-1e02-4aa6-9bf1-3e56c3a23da4@linux.dev> (raw)
In-Reply-To: <26c4677b-aeff-4516-85f4-87b5d1a9f6ee@meta.com>
On 11/26/25 7:56 AM, Chris Mason wrote:
>
>
> On 11/26/25 10:24 AM, Leon Hwang wrote:
>>
>>
>> On 2025/11/26 23:11, bot+bpf-ci@kernel.org wrote:
>>>> diff --git a/include/linux/bpf.h b/include/linux/bpf.h
>>>> index d84af3719..01a99e3a3 100644
>>>> --- a/include/linux/bpf.h
>>>> +++ b/include/linux/bpf.h
>>>
>>> [ ... ]
>>>
>>>> diff --git a/kernel/bpf/arraymap.c b/kernel/bpf/arraymap.c
>>>> index 1eeb31c5b..67e9e811d 100644
>>>> --- a/kernel/bpf/arraymap.c
>>>> +++ b/kernel/bpf/arraymap.c
>>>
>>> [ ... ]
>>>
>>>> @@ -398,10 +405,11 @@ int bpf_percpu_array_update(struct bpf_map *map, void *key, void *value,
>>>> struct bpf_array *array = container_of(map, struct bpf_array, map);
>>>> u32 index = *(u32 *)key;
>>>> void __percpu *pptr;
>>>> - int cpu, off = 0;
>>>> + void *ptr, *val;
>>>> u32 size;
>>>> + int cpu;
>>>>
>>>> - if (unlikely(map_flags > BPF_EXIST))
>>>> + if (unlikely((map_flags & BPF_F_LOCK) || (u32)map_flags > BPF_F_ALL_CPUS))
>>>> /* unknown flags */
>>>> return -EINVAL;
>>>>
>>>> @@ -409,7 +417,7 @@ int bpf_percpu_array_update(struct bpf_map *map, void *key, void *value,
>>>> /* all elements were pre-allocated, cannot insert a new one */
>>>> return -E2BIG;
>>>>
>>>> - if (unlikely(map_flags & BPF_NOEXIST))
>>>> + if (unlikely(map_flags == BPF_NOEXIST))
>>> ^^
>>>
>>
>> ?
>>
>> No such change in this version.
>>
>> It seems that this change was inferred from v11 to v12 by AI itself
>
> Thanks for flagging this, I'll try to find this section of the logs to
> see how the false positive checks failed to catch it.
>
> -chris
AI got confused here, this was not in the diff.
But it appears it got triggered, because there are these two code
fragments nearby [1]:
if (unlikely(map_flags & BPF_NOEXIST))
/* all elements already exist */
return -EEXIST;
and
if (unlikely(map_flags == BPF_NOEXIST))
/* all elements already exist */
return -EEXIST;
Which is a good thing to notice even if this is intentional.
Anyone knows if it is?
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/tree/kernel/bpf/arraymap.c#n356
>
next prev parent reply other threads:[~2025-11-26 22:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 14:50 [PATCH bpf-next v12 0/7] bpf: Introduce BPF_F_CPU and BPF_F_ALL_CPUS flags for percpu maps Leon Hwang
2025-11-26 14:50 ` [PATCH bpf-next v12 1/7] bpf: Introduce BPF_F_CPU and BPF_F_ALL_CPUS flags Leon Hwang
2025-11-26 14:50 ` [PATCH bpf-next v12 2/7] bpf: Add BPF_F_CPU and BPF_F_ALL_CPUS flags support for percpu_array maps Leon Hwang
2025-11-26 15:11 ` bot+bpf-ci
2025-11-26 15:24 ` Leon Hwang
2025-11-26 15:56 ` Chris Mason
2025-11-26 22:20 ` Ihor Solodrai [this message]
2025-11-26 14:50 ` [PATCH bpf-next v12 3/7] bpf: Add BPF_F_CPU and BPF_F_ALL_CPUS flags support for percpu_hash and lru_percpu_hash maps Leon Hwang
2025-11-26 15:11 ` bot+bpf-ci
2025-11-26 16:24 ` Leon Hwang
2025-11-26 14:50 ` [PATCH bpf-next v12 4/7] bpf: Copy map value using copy_map_value_long for percpu_cgroup_storage maps Leon Hwang
2025-11-26 14:50 ` [PATCH bpf-next v12 5/7] bpf: Add BPF_F_CPU and BPF_F_ALL_CPUS flags support " Leon Hwang
2025-11-26 15:11 ` bot+bpf-ci
2025-11-26 15:35 ` Leon Hwang
2025-11-26 14:50 ` [PATCH bpf-next v12 6/7] libbpf: Add BPF_F_CPU and BPF_F_ALL_CPUS flags support for percpu maps Leon Hwang
2025-11-26 14:50 ` [PATCH bpf-next v12 7/7] selftests/bpf: Add cases to test BPF_F_CPU and BPF_F_ALL_CPUS flags Leon Hwang
2026-01-06 18:25 ` [PATCH bpf-next v12 0/7] bpf: Introduce BPF_F_CPU and BPF_F_ALL_CPUS flags for percpu maps Alexei Starovoitov
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=68ecc660-1e02-4aa6-9bf1-3e56c3a23da4@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=a.s.protopopov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chen.dylane@linux.dev \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=deso@posteo.net \
--cc=dxu@dxuuu.xyz \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-patches-bot@fb.com \
--cc=kerneljasonxing@gmail.com \
--cc=kpsingh@kernel.org \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=paul.chaignon@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tklauser@distanz.ch \
--cc=willemb@google.com \
--cc=yatsenko@meta.com \
--cc=yonghong.song@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.