All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: zhoufeng <zhoufeng.zf@bytedance.com>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, kuznet@ms2.inr.ac.ru,
	duanxiongchun@bytedance.com, wangdongdong.6@bytedance.com,
	chenzhuowen.simon@bytedance.com
Subject: Re: [PATCH] lib/bpf: Fix btf_load error lead to enable debug log
Date: Thu, 29 Jul 2021 12:02:20 +0800	[thread overview]
Message-ID: <f4e53471-aa20-3579-6d44-85e6b3524b9f@bytedance.com> (raw)
In-Reply-To: <20210728093321.16500-1-zhoufeng.zf@bytedance.com>



在 2021/7/28 下午5:33, Feng zhou 写道:
> From: Feng Zhou <zhoufeng.zf@bytedance.com>
> 
> Use tc with no verbose, when bpf_btf_attach fail,
> the conditions:
> "if (fd < 0 && (errno == ENOSPC || !ctx->log_size))"
> will make ctx->log_size != 0. And then, bpf_prog_attach,
> ctx->log_size != 0. so enable debug log.
> The verifier log sometimes is so chatty on larger programs.
> bpf_prog_attach is failed.
> "Log buffer too small to dump verifier log 16777215 bytes (9 tries)!"
> 
> BTF load failure does not affect prog load. prog still work.
> So when BTF/PROG load fail, enlarge log_size and re-fail with
> having verbose.
> 
> Signed-off-by: Feng Zhou <zhoufeng.zf@bytedance.com>
> ---
>   lib/bpf_legacy.c | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/lib/bpf_legacy.c b/lib/bpf_legacy.c
> index 8a03b9c2..80c49f08 100644
> --- a/lib/bpf_legacy.c
> +++ b/lib/bpf_legacy.c
> @@ -1525,13 +1525,13 @@ retry:
>   	fd = bpf_prog_load_dev(prog->type, prog->insns, prog->size,
>   			       prog->license, ctx->ifindex,
>   			       ctx->log, ctx->log_size);
> -	if (fd < 0 || ctx->verbose) {
> +	if (fd < 0 && ctx->verbose) {
>   		/* The verifier log is pretty chatty, sometimes so chatty
>   		 * on larger programs, that we could fail to dump everything
>   		 * into our buffer. Still, try to give a debuggable error
>   		 * log for the user, so enlarge it and re-fail.
>   		 */
> -		if (fd < 0 && (errno == ENOSPC || !ctx->log_size)) {
> +		if (errno == ENOSPC) {
>   			if (tries++ < 10 && !bpf_log_realloc(ctx))
>   				goto retry;
>   
> @@ -2068,8 +2068,8 @@ retry:
>   	errno = 0;
>   	fd = bpf_btf_load(ctx->btf_data->d_buf, ctx->btf_data->d_size,
>   			  ctx->log, ctx->log_size);
> -	if (fd < 0 || ctx->verbose) {
> -		if (fd < 0 && (errno == ENOSPC || !ctx->log_size)) {
> +	if (fd < 0 && ctx->verbose) {
> +		if (errno == ENOSPC) {
>   			if (tries++ < 10 && !bpf_log_realloc(ctx))
>   				goto retry;
>   
> 

Sorry, this patch is wrong. please ignore it. I will send a new one.

  reply	other threads:[~2021-07-29  4:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28  9:33 [PATCH] lib/bpf: Fix btf_load error lead to enable debug log Feng zhou
2021-07-29  4:02 ` zhoufeng [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-29  4:55 Feng zhou
2021-07-30 18:40 ` 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=f4e53471-aa20-3579-6d44-85e6b3524b9f@bytedance.com \
    --to=zhoufeng.zf@bytedance.com \
    --cc=chenzhuowen.simon@bytedance.com \
    --cc=duanxiongchun@bytedance.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=wangdongdong.6@bytedance.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.