From: Jiri Olsa <jolsa@redhat.com>
To: John Fastabend <john.fastabend@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
Yonghong Song <yhs@fb.com>, Martin KaFai Lau <kafai@fb.com>,
Jakub Kicinski <kuba@kernel.org>, David Miller <davem@redhat.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Andrii Nakryiko <andriin@fb.com>, KP Singh <kpsingh@chromium.org>,
Masanori Misono <m.misono760@gmail.com>
Subject: Re: [PATCH] bpf: Allow small structs to be type of function argument
Date: Thu, 18 Jun 2020 13:48:06 +0200 [thread overview]
Message-ID: <20200618114806.GA2369163@krava> (raw)
In-Reply-To: <5eeaa556c7a0e_38b82b28075185c46a@john-XPS-13-9370.notmuch>
On Wed, Jun 17, 2020 at 04:20:54PM -0700, John Fastabend wrote:
> Jiri Olsa wrote:
> > This way we can have trampoline on function
> > that has arguments with types like:
> >
> > kuid_t uid
> > kgid_t gid
> >
> > which unwind into small structs like:
> >
> > typedef struct {
> > uid_t val;
> > } kuid_t;
> >
> > typedef struct {
> > gid_t val;
> > } kgid_t;
> >
> > And we can use them in bpftrace like:
> > (assuming d_path changes are in)
> >
> > # bpftrace -e 'lsm:path_chown { printf("uid %d, gid %d\n", args->uid, args->gid) }'
> > Attaching 1 probe...
> > uid 0, gid 0
> > uid 1000, gid 1000
> > ...
> >
> > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > ---
> > kernel/bpf/btf.c | 12 +++++++++++-
> > 1 file changed, 11 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> > index 58c9af1d4808..f8fee5833684 100644
> > --- a/kernel/bpf/btf.c
> > +++ b/kernel/bpf/btf.c
> > @@ -362,6 +362,14 @@ static bool btf_type_is_struct(const struct btf_type *t)
> > return kind == BTF_KIND_STRUCT || kind == BTF_KIND_UNION;
> > }
> >
> > +/* type is struct and its size is within 8 bytes
> > + * and it can be value of function argument
> > + */
> > +static bool btf_type_is_struct_arg(const struct btf_type *t)
> > +{
> > + return btf_type_is_struct(t) && (t->size <= sizeof(u64));
>
> Can you comment on why sizeof(u64) here? The int types can be larger
> than 64 for example and don't have a similar check, maybe the should
> as well?
>
> Here is an example from some made up program I ran through clang and
> bpftool.
>
> [2] INT '__int128' size=16 bits_offset=0 nr_bits=128 encoding=SIGNED
>
> We also have btf_type_int_is_regular to decide if the int is of some
> "regular" size but I don't see it used in these paths.
so this small structs are passed as scalars via function arguments,
so the size limit is to fit teir value into register size which holds
the argument
I'm not sure how 128bit numbers are passed to function as argument,
but I think we can treat them separately if there's a need
jirka
>
> > +}
> > +
> > static bool __btf_type_is_struct(const struct btf_type *t)
> > {
> > return BTF_INFO_KIND(t->info) == BTF_KIND_STRUCT;
> > @@ -3768,7 +3776,7 @@ bool btf_ctx_access(int off, int size, enum bpf_access_type type,
> > /* skip modifiers */
> > while (btf_type_is_modifier(t))
> > t = btf_type_by_id(btf, t->type);
> > - if (btf_type_is_int(t) || btf_type_is_enum(t))
> > + if (btf_type_is_int(t) || btf_type_is_enum(t) || btf_type_is_struct_arg(t))
> > /* accessing a scalar */
> > return true;
> > if (!btf_type_is_ptr(t)) {
> > @@ -4161,6 +4169,8 @@ static int __get_type_size(struct btf *btf, u32 btf_id,
> > return sizeof(void *);
> > if (btf_type_is_int(t) || btf_type_is_enum(t))
> > return t->size;
> > + if (btf_type_is_struct_arg(t))
> > + return t->size;
> > *bad_type = t;
> > return -EINVAL;
> > }
> > --
> > 2.25.4
> >
>
>
next prev parent reply other threads:[~2020-06-18 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 17:35 [PATCH] bpf: Allow small structs to be type of function argument Jiri Olsa
2020-06-17 23:20 ` John Fastabend
2020-06-18 11:48 ` Jiri Olsa [this message]
2020-06-18 22:05 ` Alexei Starovoitov
2020-06-19 8:50 ` Jiri Olsa
2020-06-18 22:06 ` John Fastabend
2020-06-18 23:59 ` Andrii Nakryiko
2020-06-19 0:25 ` John Fastabend
2020-06-19 2:04 ` Alexei Starovoitov
2020-06-19 5:39 ` Yonghong Song
2020-06-19 17:44 ` John Fastabend
2020-06-19 18:56 ` Yonghong Song
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=20200618114806.GA2369163@krava \
--to=jolsa@redhat.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@redhat.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kuba@kernel.org \
--cc=m.misono760@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yhs@fb.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