From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: 梦龙董 <dongmenglong.8@bytedance.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eddy Z <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
X86 ML <x86@kernel.org>, Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Quentin Monnet <quentin@isovalent.com>,
bpf <bpf@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
linux-trace-kernel@vger.kernel.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [External] Re: [PATCH bpf-next v2 1/9] bpf: tracing: add support to record and check the accessed args
Date: Mon, 11 Mar 2024 19:09:25 -0700 [thread overview]
Message-ID: <CAADnVQJ_ZCzMmT1aBsNXEBFfYNSVBdBXmLocjR0PPEWtYQrQFw@mail.gmail.com> (raw)
In-Reply-To: <CALz3k9i5G5wWi+rtvHPwVLOUAXVMCiU_8QUZs87TEYgR_0wpPA@mail.gmail.com>
On Mon, Mar 11, 2024 at 7:01 PM 梦龙董 <dongmenglong.8@bytedance.com> wrote:
>
> On Tue, Mar 12, 2024 at 9:46 AM Alexei Starovoitov
> <alexei.starovoitov@gmail.com> wrote:
> >
> > On Mon, Mar 11, 2024 at 2:34 AM Menglong Dong
> > <dongmenglong.8@bytedance.com> wrote:
> > >
> > > In this commit, we add the 'accessed_args' field to struct bpf_prog_aux,
> > > which is used to record the accessed index of the function args in
> > > btf_ctx_access().
> > >
> > > Meanwhile, we add the function btf_check_func_part_match() to compare the
> > > accessed function args of two function prototype. This function will be
> > > used in the following commit.
> > >
> > > Signed-off-by: Menglong Dong <dongmenglong.8@bytedance.com>
> > > ---
> > > include/linux/bpf.h | 4 ++
> > > kernel/bpf/btf.c | 108 +++++++++++++++++++++++++++++++++++++++++++-
> > > 2 files changed, 110 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/include/linux/bpf.h b/include/linux/bpf.h
> > > index 95e07673cdc1..0f677fdcfcc7 100644
> > > --- a/include/linux/bpf.h
> > > +++ b/include/linux/bpf.h
> > > @@ -1461,6 +1461,7 @@ struct bpf_prog_aux {
> > > const struct btf_type *attach_func_proto;
> > > /* function name for valid attach_btf_id */
> > > const char *attach_func_name;
> > > + u64 accessed_args;
> > > struct bpf_prog **func;
> > > void *jit_data; /* JIT specific data. arch dependent */
> > > struct bpf_jit_poke_descriptor *poke_tab;
> > > @@ -2565,6 +2566,9 @@ struct bpf_reg_state;
> > > int btf_prepare_func_args(struct bpf_verifier_env *env, int subprog);
> > > int btf_check_type_match(struct bpf_verifier_log *log, const struct bpf_prog *prog,
> > > struct btf *btf, const struct btf_type *t);
> > > +int btf_check_func_part_match(struct btf *btf1, const struct btf_type *t1,
> > > + struct btf *btf2, const struct btf_type *t2,
> > > + u64 func_args);
> > > const char *btf_find_decl_tag_value(const struct btf *btf, const struct btf_type *pt,
> > > int comp_idx, const char *tag_key);
> > > int btf_find_next_decl_tag(const struct btf *btf, const struct btf_type *pt,
> > > diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> > > index 170d017e8e4a..c2a0299d4358 100644
> > > --- a/kernel/bpf/btf.c
> > > +++ b/kernel/bpf/btf.c
> > > @@ -6125,19 +6125,24 @@ static bool is_int_ptr(struct btf *btf, const struct btf_type *t)
> > > }
> > >
> > > static u32 get_ctx_arg_idx(struct btf *btf, const struct btf_type *func_proto,
> > > - int off)
> > > + int off, int *aligned_idx)
> > > {
> > > const struct btf_param *args;
> > > const struct btf_type *t;
> > > u32 offset = 0, nr_args;
> > > int i;
> > >
> > > + if (aligned_idx)
> > > + *aligned_idx = -ENOENT;
> > > +
> > > if (!func_proto)
> > > return off / 8;
> > >
> > > nr_args = btf_type_vlen(func_proto);
> > > args = (const struct btf_param *)(func_proto + 1);
> > > for (i = 0; i < nr_args; i++) {
> > > + if (aligned_idx && offset == off)
> > > + *aligned_idx = i;
> > > t = btf_type_skip_modifiers(btf, args[i].type, NULL);
> > > offset += btf_type_is_ptr(t) ? 8 : roundup(t->size, 8);
> > > if (off < offset)
> > > @@ -6207,7 +6212,7 @@ bool btf_ctx_access(int off, int size, enum bpf_access_type type,
> > > tname, off);
> > > return false;
> > > }
> > > - arg = get_ctx_arg_idx(btf, t, off);
> > > + arg = get_ctx_arg_idx(btf, t, off, NULL);
> > > args = (const struct btf_param *)(t + 1);
> > > /* if (t == NULL) Fall back to default BPF prog with
> > > * MAX_BPF_FUNC_REG_ARGS u64 arguments.
> > > @@ -6217,6 +6222,9 @@ bool btf_ctx_access(int off, int size, enum bpf_access_type type,
> > > /* skip first 'void *__data' argument in btf_trace_##name typedef */
> > > args++;
> > > nr_args--;
> > > + prog->aux->accessed_args |= (1 << (arg + 1));
> > > + } else {
> > > + prog->aux->accessed_args |= (1 << arg);
> >
> > What do you need this aligned_idx for ?
> > I'd expect that above "accessed_args |= (1 << arg);" is enough.
> >
>
> Which aligned_idx? No aligned_idx in the btf_ctx_access(), and
> aligned_idx is only used in the btf_check_func_part_match().
>
> In the btf_check_func_part_match(), I need to compare the
> t1->args[i] and t2->args[j], which have the same offset. And
> the aligned_idx is to find the "j" according to the offset of
> t1->args[i].
And that's my question.
Why you don't do the max of accessed_args across all attach
points and do btf_check_func_type_match() to that argno
instead of nargs1.
This 'offset += btf_type_is_ptr(t1) ? 8 : roundup...
is odd.
next prev parent reply other threads:[~2024-03-12 2:09 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 9:35 [PATCH bpf-next v2 0/9] bpf: make tracing program support multi-link Menglong Dong
2024-03-11 9:35 ` [PATCH bpf-next v2 1/9] bpf: tracing: add support to record and check the accessed args Menglong Dong
2024-03-12 1:46 ` Alexei Starovoitov
2024-03-12 2:01 ` [External] " 梦龙董
2024-03-12 2:09 ` Alexei Starovoitov [this message]
2024-03-12 2:42 ` 梦龙董
2024-03-12 2:49 ` 梦龙董
2024-03-12 16:42 ` Alexei Starovoitov
2024-03-13 1:53 ` 梦龙董
2024-03-14 0:25 ` Alexei Starovoitov
2024-03-14 6:27 ` Jiri Olsa
2024-03-15 8:17 ` 梦龙董
2024-03-15 8:00 ` 梦龙董
2024-03-28 14:43 ` 梦龙董
2024-03-28 15:13 ` Steven Rostedt
2024-03-28 23:17 ` Alexei Starovoitov
2024-03-30 3:36 ` 梦龙董
2024-03-29 23:28 ` Andrii Nakryiko
2024-03-29 23:28 ` Andrii Nakryiko
2024-03-29 23:28 ` Andrii Nakryiko
2024-03-30 4:16 ` 梦龙董
2024-03-30 12:27 ` Steven Rostedt
2024-03-30 17:52 ` Jiri Olsa
2024-03-31 2:34 ` Andrii Nakryiko
2024-03-31 2:34 ` Andrii Nakryiko
2024-03-30 3:18 ` 梦龙董
2024-03-30 19:37 ` Steven Rostedt
2024-04-01 2:28 ` 梦龙董
2024-04-01 15:59 ` Steven Rostedt
2024-03-11 9:35 ` [PATCH bpf-next v2 2/9] bpf: refactor the modules_array to ptr_array Menglong Dong
2024-03-12 1:48 ` Alexei Starovoitov
2024-03-12 1:53 ` [External] " 梦龙董
2024-03-11 9:35 ` [PATCH bpf-next v2 3/9] bpf: trampoline: introduce struct bpf_tramp_link_conn Menglong Dong
2024-03-11 9:35 ` [PATCH bpf-next v2 4/9] bpf: trampoline: introduce bpf_tramp_multi_link Menglong Dong
2024-03-11 9:35 ` [PATCH bpf-next v2 5/9] bpf: verifier: add btf to the function args of bpf_check_attach_target Menglong Dong
2024-03-12 1:51 ` Alexei Starovoitov
2024-03-12 3:13 ` [External] " 梦龙董
2024-03-11 9:35 ` [PATCH bpf-next v2 6/9] bpf: tracing: add multi-link support Menglong Dong
2024-03-11 18:59 ` kernel test robot
2024-03-11 21:36 ` kernel test robot
2024-03-11 9:35 ` [PATCH bpf-next v2 7/9] libbpf: don't free btf if program of multi-link tracing existing Menglong Dong
2024-03-12 1:55 ` Alexei Starovoitov
2024-03-12 2:05 ` [External] " 梦龙董
2024-03-12 2:13 ` Alexei Starovoitov
2024-03-12 2:56 ` 梦龙董
2024-03-11 9:35 ` [PATCH bpf-next v2 8/9] libbpf: add support for the multi-link of tracing Menglong Dong
2024-03-11 15:29 ` Quentin Monnet
2024-03-12 1:43 ` [External] " 梦龙董
2024-03-12 1:56 ` Alexei Starovoitov
2024-03-12 2:44 ` [External] " 梦龙董
2024-03-12 16:11 ` Alexei Starovoitov
2024-03-13 1:14 ` 梦龙董
2024-03-11 9:35 ` [PATCH bpf-next v2 9/9] selftests/bpf: add testcases for " Menglong Dong
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=CAADnVQJ_ZCzMmT1aBsNXEBFfYNSVBdBXmLocjR0PPEWtYQrQFw@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dongmenglong.8@bytedance.com \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=svens@linux.ibm.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).