All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Masoud Aghasi <maghasi@disroot.org>
Cc: bpf@vger.kernel.org, andrii@kernel.org, eddyz87@gmail.com,
	ast@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
	martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
	jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
	leon.hwang@linux.dev, john.fastabend@gmail.com
Subject: Re: [PATCH bpf v6 0/3] bpf: Fix incorrect handling of user flags by percpu map updates
Date: Sun, 18 Oct 2026 23:00:06 +0000	[thread overview]
Message-ID: <179236440678.1848710.9466674837346626219.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008120734.1565972-1-maghasi@disroot.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu,  8 Oct 2026 13:07:31 +0100 you wrote:
> For BPF_MAP_TYPE_PERCPU_ARRAY map, bpf_percpu_array_update()
> is not considering the possibility of a combination of
> (BPF_NOEXIST, BPF_EXIST) flags with (BPF_F_CPU, BPF_F_ALL_CPUS) flags.
> This causes the (BPF_NOEXIST, BPF_EXIST) flags to lose their effect
> in some cases.
> 
> For BPF_MAP_TYPE_PERCPU_HASH and BPF_MAP_TYPE_LRU_PERCPU_HASH maps,
> htab_map_check_update_flags() and check_flags() are not considering
> the possibility of a combination of (BPF_NOEXIST, BPF_EXIST) flags
> with (BPF_F_CPU, BPF_F_ALL_CPUS) flags. This causes the
> (BPF_NOEXIST, BPF_EXIST) flags to lose their effect in some cases.
> 
> [...]

Here is the summary with links:
  - [bpf,v6,1/3] bpf: Fix incorrect handling of user flags in bpf_percpu_array_update
    https://git.kernel.org/bpf/bpf-next/c/a898ff0f3e99
  - [bpf,v6,2/3] bpf: Fix incorrect handling of user flags by percpu hash map updates
    https://git.kernel.org/bpf/bpf-next/c/4a9b25fe8d13
  - [bpf,v6,3/3] selftests/bpf: add tests for percpu map flags combination
    https://git.kernel.org/bpf/bpf-next/c/22392799e251

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-18 23:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 12:07 [PATCH bpf v6 0/3] bpf: Fix incorrect handling of user flags by percpu map updates Masoud Aghasi
2026-10-08 12:07 ` [PATCH bpf v6 1/3] bpf: Fix incorrect handling of user flags in bpf_percpu_array_update Masoud Aghasi
2026-10-08 13:27   ` Leon Hwang
2026-10-08 12:07 ` [PATCH bpf v6 2/3] bpf: Fix incorrect handling of user flags by percpu hash map updates Masoud Aghasi
2026-10-08 13:27   ` Leon Hwang
2026-10-08 12:07 ` [PATCH bpf v6 3/3] selftests/bpf: add tests for percpu map flags combination Masoud Aghasi
2026-10-08 13:28   ` Leon Hwang
2026-10-08 15:58     ` Masoud Aghasi
2026-10-18 23:00 ` patchwork-bot+netdevbpf [this message]

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=179236440678.1848710.9466674837346626219.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=leon.hwang@linux.dev \
    --cc=maghasi@disroot.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=song@kernel.org \
    --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.