From: Eduard Zingerman <eddyz87@gmail.com>
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
ameryhung@gmail.com
Cc: Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf-next 1/2] bpf: Introduce struct bpf_map_desc in verifier
Date: Thu, 29 Jan 2026 10:36:12 -0800 [thread overview]
Message-ID: <073acdfedcc2181f0eb343cb16efcd4c244cd1ce.camel@gmail.com> (raw)
In-Reply-To: <20260129-verif_special_fields-v1-1-d310b7f146c8@meta.com>
On Thu, 2026-01-29 at 17:38 +0000, Mykyta Yatsenko wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> Introduce struct bpf_map_desc to hold bpf_map pointer and map uid. Use
> this struct in both bpf_call_arg_meta and bpf_kfunc_call_arg_meta
> instead of having different representations:
> - bpf_call_arg_meta had separate map_ptr and map_uid fields
> - bpf_kfunc_call_arg_meta had an anonymous inline struct
>
> This unifies the map fields layout across both metadata structures,
> making the code more consistent and preparing for further refactoring of
> map field pointer validation.
>
> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
> ---
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
[...]
next prev parent reply other threads:[~2026-01-29 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 17:38 [PATCH bpf-next 0/2] bpf: Unify special map field validation in verifier Mykyta Yatsenko
2026-01-29 17:38 ` [PATCH bpf-next 1/2] bpf: Introduce struct bpf_map_desc " Mykyta Yatsenko
2026-01-29 18:09 ` Amery Hung
2026-01-30 15:46 ` Mykyta Yatsenko
2026-01-30 16:00 ` Alexei Starovoitov
2026-01-29 18:36 ` Eduard Zingerman [this message]
2026-01-29 17:38 ` [PATCH bpf-next 2/2] bpf: Consolidate special map field validation " Mykyta Yatsenko
2026-01-29 18:34 ` Eduard Zingerman
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=073acdfedcc2181f0eb343cb16efcd4c244cd1ce.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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