From: Martin Lau <kafai@fb.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David Miller" <davem@davemloft.net>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH v3 bpf-next 2/3] bpf: Add array support to btf_struct_access
Date: Thu, 7 Nov 2019 17:22:47 +0000 [thread overview]
Message-ID: <20191107172243.ptq3yqeacxjkmkbq@kafai-mbp> (raw)
In-Reply-To: <CAEf4BzaQOEjbJwV9Ycb1QdBVkFRQLB_3cyw1sfXTz-iV_pt4Yw@mail.gmail.com>
On Wed, Nov 06, 2019 at 06:41:15PM -0800, Andrii Nakryiko wrote:
> On Wed, Nov 6, 2019 at 5:49 PM Martin KaFai Lau <kafai@fb.com> wrote:
> >
> > This patch adds array support to btf_struct_access().
> > It supports array of int, array of struct and multidimensional
> > array.
> >
> > It also allows using u8[] as a scratch space. For example,
> > it allows access the "char cb[48]" with size larger than
> > the array's element "char". Another potential use case is
> > "u64 icsk_ca_priv[]" in the tcp congestion control.
> >
> > btf_resolve_size() is added to resolve the size of any type.
> > It will follow the modifier if there is any. Please
> > see the function comment for details.
> >
> > This patch also adds the "off < moff" check at the beginning
> > of the for loop. It is to reject cases when "off" is pointing
> > to a "hole" in a struct.
> >
> > Signed-off-by: Martin KaFai Lau <kafai@fb.com>
> > ---
>
> Looks good, just two small nits.
>
> Acked-by: Andrii Nakryiko <andriin@fb.com>
>
> > kernel/bpf/btf.c | 187 +++++++++++++++++++++++++++++++++++++++--------
> > 1 file changed, 157 insertions(+), 30 deletions(-)
> >
> > diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> > index 128d89601d73..5c4b6aa7b9f0 100644
> > --- a/kernel/bpf/btf.c
> > +++ b/kernel/bpf/btf.c
> > @@ -1036,6 +1036,82 @@ static const struct resolve_vertex *env_stack_peak(struct btf_verifier_env *env)
> > return env->top_stack ? &env->stack[env->top_stack - 1] : NULL;
> > }
> >
>
> [...]
>
> > - if (off + size <= moff / 8)
> > - /* won't find anything, field is already too far */
> > + /* offset of the field in bytes */
> > + moff = btf_member_bit_offset(t, member) / 8;
> > + if (off + size <= moff)
>
> you dropped useful comment :(
good catch. will undo.
>
> > break;
> > + /* In case of "off" is pointing to holes of a struct */
> > + if (off < moff)
> > + continue;
> >
>
> [...]
>
> > +
> > + mtrue_end = moff + msize;
>
> nit: there is no other _end, so might be just mend (in line with moff)
I prefer to keep it. For array, this _end is not the end of mtype.
The intention is to distinguish it from the mtype/msize convention
such that it is the true_end of the current struct's member. I will
add some comments to clarify.
>
> > + if (off >= mtrue_end)
> > /* no overlap with member, keep iterating */
> > continue;
> > +
>
> [...]
next prev parent reply other threads:[~2019-11-07 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 1:46 [PATCH v3 bpf-next 0/3] bpf: Add array support to btf_struct_access Martin KaFai Lau
2019-11-07 1:46 ` [PATCH v3 bpf-next 1/3] bpf: Account for insn->off when doing bpf_probe_read_kernel Martin KaFai Lau
2019-11-07 2:45 ` Andrii Nakryiko
2019-11-07 5:57 ` Alexei Starovoitov
2019-11-07 1:46 ` [PATCH v3 bpf-next 2/3] bpf: Add array support to btf_struct_access Martin KaFai Lau
2019-11-07 2:41 ` Andrii Nakryiko
2019-11-07 17:22 ` Martin Lau [this message]
2019-11-07 17:26 ` Andrii Nakryiko
2019-11-07 1:46 ` [PATCH v3 bpf-next 3/3] bpf: Add cb access in kfree_skb test Martin KaFai Lau
2019-11-07 2:50 ` Andrii Nakryiko
2019-11-07 17:29 ` Martin Lau
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=20191107172243.ptq3yqeacxjkmkbq@kafai-mbp \
--to=kafai@fb.com \
--cc=Kernel-team@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).