From: Yonghong Song <yonghong.song@linux.dev>
To: Philo Lu <lulie@linux.alibaba.com>, bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
shuah@kernel.org, xuanzhuo@linux.alibaba.com
Subject: Re: [PATCH bpf-next 1/3] bpf: store both map ptr and state in bpf_insn_aux_data
Date: Thu, 4 Apr 2024 15:08:11 -0700 [thread overview]
Message-ID: <05dfc9a1-d572-4cf1-aa9f-bbe37b7c881e@linux.dev> (raw)
In-Reply-To: <20240402061615.48894-2-lulie@linux.alibaba.com>
On 4/1/24 11:16 PM, Philo Lu wrote:
> Currently, bpf_insn_aux_data->map_ptr_state is used to store either
> map_ptr or its poison state (i.e., BPF_MAP_PTR_POISON). Thus
> BPF_MAP_PTR_POISON must be checked before reading map_ptr. However we do
> need both of them sometimes, e.g., in bpf_for_each_map_elem() helper ().
You can say:
In certain cases, we may need valid map_ptr even in case of poison state.
This will be explained in next patch with bpf_for_each_map_elem() helper.
>
> This patch changes map_ptr_state into a new struct including both map
> pointer and its state (poison/unpriv). It's in the same union with
> struct bpf_loop_inline_state, so there is no extra memory overhead.
> Besides, macros BPF_MAP_PTR_UNPRIV/BPF_MAP_PTR_POISON/BPF_MAP_PTR are no
> longer needed.
You can further mention that this patch does not change any
existing functionality.
>
> Signed-off-by: Philo Lu <lulie@linux.alibaba.com>
> ---
> include/linux/bpf_verifier.h | 9 ++++++++-
> kernel/bpf/verifier.c | 36 ++++++++++++++++--------------------
> 2 files changed, 24 insertions(+), 21 deletions(-)
>
> diff --git a/include/linux/bpf_verifier.h b/include/linux/bpf_verifier.h
> index 7cb1b75eee38..1b5d6c7bb4e0 100644
> --- a/include/linux/bpf_verifier.h
> +++ b/include/linux/bpf_verifier.h
> @@ -502,6 +502,13 @@ struct bpf_loop_inline_state {
> u32 callback_subprogno; /* valid when fit_for_inline is true */
> };
>
> +/* pointer and state for maps */
> +struct bpf_map_ptr_state {
> + struct bpf_map *map_ptr;
> + unsigned int poison:1;
> + unsigned int unpriv:1;
Let us change 'unsigned int' to 'bool' which is more appropriate.
> +};
> +
> /* Possible states for alu_state member. */
> #define BPF_ALU_SANITIZE_SRC (1U << 0)
> #define BPF_ALU_SANITIZE_DST (1U << 1)
> @@ -514,7 +521,7 @@ struct bpf_loop_inline_state {
> struct bpf_insn_aux_data {
> union {
> enum bpf_reg_type ptr_type; /* pointer type for load/store insns */
> - unsigned long map_ptr_state; /* pointer/poison value for maps */
> + struct bpf_map_ptr_state map_ptr_state;
> s32 call_imm; /* saved imm field of call insn */
> u32 alu_limit; /* limit for add/sub register with pointer */
> struct {
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index edb650667f44..515ac6165ab1 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -190,11 +190,6 @@ struct bpf_verifier_stack_elem {
> #define BPF_MAP_KEY_POISON (1ULL << 63)
> #define BPF_MAP_KEY_SEEN (1ULL << 62)
>
> -#define BPF_MAP_PTR_UNPRIV 1UL
> -#define BPF_MAP_PTR_POISON ((void *)((0xeB9FUL << 1) + \
> - POISON_POINTER_DELTA))
> -#define BPF_MAP_PTR(X) ((struct bpf_map *)((X) & ~BPF_MAP_PTR_UNPRIV))
> -
> #define BPF_GLOBAL_PERCPU_MA_MAX_SIZE 512
>
> static int acquire_reference_state(struct bpf_verifier_env *env, int insn_idx);
> @@ -209,21 +204,22 @@ static bool is_trusted_reg(const struct bpf_reg_state *reg);
>
> static bool bpf_map_ptr_poisoned(const struct bpf_insn_aux_data *aux)
> {
> - return BPF_MAP_PTR(aux->map_ptr_state) == BPF_MAP_PTR_POISON;
> + return !!aux->map_ptr_state.poison;
with 'poison' is bool type, just return aux->map_ptr_state.poison.
> }
>
> static bool bpf_map_ptr_unpriv(const struct bpf_insn_aux_data *aux)
> {
> - return aux->map_ptr_state & BPF_MAP_PTR_UNPRIV;
> + return !!aux->map_ptr_state.unpriv;
return aux->map_ptr_state.unpriv.
> }
>
> static void bpf_map_ptr_store(struct bpf_insn_aux_data *aux,
> - const struct bpf_map *map, bool unpriv)
> + struct bpf_map *map,
> + bool unpriv, bool poison)
> {
> - BUILD_BUG_ON((unsigned long)BPF_MAP_PTR_POISON & BPF_MAP_PTR_UNPRIV);
> unpriv |= bpf_map_ptr_unpriv(aux);
> - aux->map_ptr_state = (unsigned long)map |
> - (unpriv ? BPF_MAP_PTR_UNPRIV : 0UL);
> + aux->map_ptr_state.unpriv = unpriv;
> + aux->map_ptr_state.poison = poison;
> + aux->map_ptr_state.map_ptr = map;
> }
>
[...]
next prev parent reply other threads:[~2024-04-04 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 6:16 [PATCH bpf-next 0/3] bpf: allow bpf_for_each_map_elem() helper with different input maps Philo Lu
2024-04-02 6:16 ` [PATCH bpf-next 1/3] bpf: store both map ptr and state in bpf_insn_aux_data Philo Lu
2024-04-04 22:08 ` Yonghong Song [this message]
2024-04-02 6:16 ` [PATCH bpf-next 2/3] bpf: allow invoking bpf_for_each_map_elem with different maps Philo Lu
2024-04-04 22:15 ` Yonghong Song
2024-04-02 6:16 ` [PATCH bpf-next 3/3] selftests/bpf: add test for bpf_for_each_map_elem() " Philo Lu
2024-04-04 22:35 ` Yonghong Song
2024-04-05 2:05 ` Philo Lu
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=05dfc9a1-d572-4cf1-aa9f-bbe37b7c881e@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=lulie@linux.alibaba.com \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=xuanzhuo@linux.alibaba.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox