All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: ast@kernel.org, linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH] bpf: plug a warn about bpf_session_cookie without CONFIG_FPROBE
Date: Sat, 1 Jun 2024 16:45:10 +0200	[thread overview]
Message-ID: <Zlsz9pTiT2Ad04i6@krava> (raw)
In-Reply-To: <20240601133224.674784-1-mjguzik@gmail.com>

On Sat, Jun 01, 2024 at 03:32:23PM +0200, Mateusz Guzik wrote:
> Building a kernel without said option results in:
> WARN: resolve_btfids: unresolved symbol bpf_session_cookie
> 
> This is a bare-minimum patch to sort it out.
> 
> There are other uses of the bpf_session_cookie thing spread out
> thorought the file, they don't seem to break anything though.
> 
> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
> ---
> 
> I don't care how this gets addressed, I just want the warning gone.
> So I am not going to fight any ideas how to do it, as long as it gets
> done.

it's fixed by:
  https://lore.kernel.org/bpf/20240531194500.2967187-1-jolsa@kernel.org/

thanks,
jirka

> 
>  kernel/bpf/verifier.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index 48f3a9acdef3..b081bdd6f477 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -11128,7 +11128,9 @@ BTF_ID(func, bpf_iter_css_task_new)
>  #else
>  BTF_ID_UNUSED
>  #endif
> +#ifdef CONFIG_FPROBES
>  BTF_ID(func, bpf_session_cookie)
> +#endif
>  
>  static bool is_kfunc_ret_null(struct bpf_kfunc_call_arg_meta *meta)
>  {
> -- 
> 2.39.2
> 
> 

      reply	other threads:[~2024-06-01 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-01 13:32 [PATCH] bpf: plug a warn about bpf_session_cookie without CONFIG_FPROBE Mateusz Guzik
2024-06-01 14:45 ` Jiri Olsa [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=Zlsz9pTiT2Ad04i6@krava \
    --to=olsajiri@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.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.