All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Martin KaFai Lau <kafai@fb.com>
Cc: jiasheng <jiasheng@iscas.ac.cn>, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH] bpf: Add env_type_is_resolved() in front of env_stack_push() in btf_resolve()
Date: Tue, 7 Sep 2021 17:25:31 -0700	[thread overview]
Message-ID: <CAEf4BzZ1KQfZKyRVn--SpvfFZMsoATrUBw4PyYhLNM97LJkePA@mail.gmail.com> (raw)
In-Reply-To: <20210907222443.gygy7eohzybpiq47@kafai-mbp.dhcp.thefacebook.com>

On Tue, Sep 7, 2021 at 3:37 PM Martin KaFai Lau <kafai@fb.com> wrote:
>
> On Thu, Sep 02, 2021 at 06:37:13AM +0000, jiasheng wrote:
> > We have found that in the complied files env_stack_push()
> > appear more than 10 times, and under at least 90% circumstances
> > that env_type_is_resolved() and env_stack_push() appear in pairs.
> > For example, they appear together in the btf_modifier_resolve()
> > of the file complie from 'kernel/bpf/btf.c'.
> > But we have found that in the btf_resolve(), there is only
> > env_stack_push() instead of the pair.
> > Therefore, we consider that the env_type_is_resolved()
> > might be forgotten.
> It does not justify a change like this just because
> one of its usage looks different and then concluded that
> it _might_ be forgotten.
>
> Does it have a bug or not?  If there is, please
> provide an explanation on how to reproduce it first.
>

Both places that call btf_resolve() check that env_type_is_resolved()
first, so there is no issue here.

> >
> > Signed-off-by: jiasheng <jiasheng@iscas.ac.cn>
> > ---
> >  kernel/bpf/btf.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> > index f982a9f0..454c249 100644
> > --- a/kernel/bpf/btf.c
> > +++ b/kernel/bpf/btf.c
> > @@ -4002,7 +4002,8 @@ static int btf_resolve(struct btf_verifier_env *env,
> >       int err = 0;
> >
> >       env->resolve_mode = RESOLVE_TBD;
> > -     env_stack_push(env, t, type_id);
> > +     if (env_type_is_resolved(env, type_id))
> > +             env_stack_push(env, t, type_id);
> >       while (!err && (v = env_stack_peak(env))) {
> >               env->log_type_id = v->type_id;
> >               err = btf_type_ops(v->t)->resolve(env, v);
> > --
> > 2.7.4
> >

  reply	other threads:[~2021-09-08  0:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02  6:37 [PATCH] bpf: Add env_type_is_resolved() in front of env_stack_push() in btf_resolve() jiasheng
2021-09-07 22:24 ` Martin KaFai Lau
2021-09-08  0:25   ` Andrii Nakryiko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-02  6:37 jiasheng
2021-09-02  6:37 jiasheng

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=CAEf4BzZ1KQfZKyRVn--SpvfFZMsoATrUBw4PyYhLNM97LJkePA@mail.gmail.com \
    --to=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=jiasheng@iscas.ac.cn \
    --cc=kafai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.