From: Borislav Petkov <bp@alien8.de>
To: Jiang Jiasheng <jiasheng@iscas.ac.cn>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] bpf: Add env_type_is_resolved() in front of env_stack_push() in btf_resolve()
Date: Thu, 2 Sep 2021 12:17:36 +0200 [thread overview]
Message-ID: <YTCkwJnIqzAqaJ5R@zn.tnic> (raw)
In-Reply-To: <1630577097-644528-1-git-send-email-jiasheng@iscas.ac.cn>
On Thu, Sep 02, 2021 at 10:04:57AM +0000, Jiang Jiasheng wrote:
> From: jiasheng <jiasheng@iscas.ac.cn>
>
> 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.
>
> 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);
> --
You still didn't read what I suggested, did you?
Because there it also explains who to CC on patches. Like, for example,
for this wrong patch you've CCed the wrong people.
Oh well, until you do, I'm deleting your mail.
Good luck.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2021-09-02 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 10:04 Jiang Jiasheng
2021-09-02 10:17 ` Borislav Petkov [this message]
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=YTCkwJnIqzAqaJ5R@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jiasheng@iscas.ac.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®