[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2333ffe38ce39b5a4d83680a53ec132cd6acbfc.camel@gmail.com>
Date: Mon, 03 Feb 2025 21:57:13 -0800
From: Eduard Zingerman <eddyz87@...il.com>
To: Amery Hung <ameryhung@...il.com>, netdev@...r.kernel.org
Cc: bpf@...r.kernel.org, daniel@...earbox.net, andrii@...nel.org,
alexei.starovoitov@...il.com, martin.lau@...nel.org, kuba@...nel.org,
edumazet@...gle.com, xiyou.wangcong@...il.com, cong.wang@...edance.com,
jhs@...atatu.com, sinquersw@...il.com, toke@...hat.com, jiri@...nulli.us,
stfomichev@...il.com, ekarani.silvestre@....ufcg.edu.br,
yangpeihao@...u.edu.cn, yepeilin.cs@...il.com, ming.lei@...hat.com,
kernel-team@...a.com
Subject: Re: [PATCH bpf-next v3 01/18] bpf: Make every prog keep a copy of
ctx_arg_info
On Fri, 2025-01-31 at 11:28 -0800, Amery Hung wrote:
> Currently, ctx_arg_info is read-only in the view of the verifier since
> it is shared among programs of the same attach type. Make each program
> have their own copy of ctx_arg_info so that we can use it to store
> program specific information.
>
> In the next patch where we support acquiring a referenced kptr through a
> struct_ops argument tagged with "__ref", ctx_arg_info->ref_obj_id will
> be used to store the unique reference object id of the argument. This
> avoids creating a requirement in the verifier that "__ref" tagged
> arguments must be the first set of references acquired [0].
>
> [0] https://lore.kernel.org/bpf/20241220195619.2022866-2-amery.hung@gmail.com/
>
> Signed-off-by: Amery Hung <ameryhung@...il.com>
> ---
Acked-by: Eduard Zingerman <eddyz87@...il.com>
[...]
Powered by blists - more mailing lists