BPF List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Andrii Nakryiko <andrii@kernel.org>,
	bpf@vger.kernel.org, ast@kernel.org,  daniel@iogearbox.net,
	martin.lau@kernel.org
Cc: kernel-team@meta.com
Subject: Re: [PATCH bpf-next 1/3] bpf: emit global subprog name in verifier logs
Date: Thu, 23 Nov 2023 17:26:48 +0200	[thread overview]
Message-ID: <800cffdb2e2fc8de9e1f2ed1a185e6a4fd0754b3.camel@gmail.com> (raw)
In-Reply-To: <20231122213112.3596548-2-andrii@kernel.org>

On Wed, 2023-11-22 at 13:31 -0800, Andrii Nakryiko wrote:
> We have the name, instead of emitting just func#N to identify global
> subprog, augment verifier log messages with actual function name to make
> it more user-friendly.
> 
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
> ---

Acked-by: Eduard Zingerman <eddyz87@gmail.com>

[...]



  reply	other threads:[~2023-11-23 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 21:31 [PATCH bpf-next 0/3] Verify global subprogs lazily Andrii Nakryiko
2023-11-22 21:31 ` [PATCH bpf-next 1/3] bpf: emit global subprog name in verifier logs Andrii Nakryiko
2023-11-23 15:26   ` Eduard Zingerman [this message]
2023-11-22 21:31 ` [PATCH bpf-next 2/3] bpf: validate global subprogs lazily Andrii Nakryiko
2023-11-23 15:26   ` Eduard Zingerman
2023-11-22 21:31 ` [PATCH bpf-next 3/3] selftests/bpf: add lazy global subprog validation tests Andrii Nakryiko
2023-11-23 15:27   ` Eduard Zingerman
2023-11-23 22:48 ` [PATCH bpf-next 0/3] Verify global subprogs lazily Daniel Borkmann
2023-11-24  3:31   ` Andrii Nakryiko

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=800cffdb2e2fc8de9e1f2ed1a185e6a4fd0754b3.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@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