public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mateusz Guzik <mjguzik@gmail.com>
To: ast@kernel.org
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
	Mateusz Guzik <mjguzik@gmail.com>
Subject: [PATCH] bpf: plug a warn about bpf_session_cookie without CONFIG_FPROBE
Date: Sat,  1 Jun 2024 15:32:23 +0200	[thread overview]
Message-ID: <20240601133224.674784-1-mjguzik@gmail.com> (raw)

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.

 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 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-01 13:32 Mateusz Guzik [this message]
2024-06-01 14:45 ` [PATCH] bpf: plug a warn about bpf_session_cookie without CONFIG_FPROBE Jiri Olsa

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=20240601133224.674784-1-mjguzik@gmail.com \
    --to=mjguzik@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.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