From: Yonghong Song <yonghong.song@linux.dev>
To: Arnd Bergmann <arnd@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Menglong Dong <menglong8.dong@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
John Fastabend <john.fastabend@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Puranjay Mohan <puranjay@kernel.org>,
Mykyta Yatsenko <yatsenko@meta.com>,
Anton Protopopov <a.s.protopopov@gmail.com>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bpf: make bpf_session_cookie() reference optional
Date: Tue, 19 May 2026 09:18:35 -0700 [thread overview]
Message-ID: <18a7fe5f-427e-44b8-9e88-b82591e1d2b7@linux.dev> (raw)
In-Reply-To: <20260515090631.284426-1-arnd@kernel.org>
On 5/15/26 2:06 AM, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> Building without CONFIG_BPF_EVENTS produces a build-time
> warning:
>
> WARN: resolve_btfids: unresolved symbol bpf_session_is_return
>
> The function is actually defined in kernel/trace/bpf_trace.o,
> which is built conditionally based on configuration.
>
> Make the reference to this function conditional as well,
> as is already done in the bpf verifier for other functions.
>
> Fixes: 8fe4dc4f6456 ("bpf: change prototype of bpf_session_{cookie,is_return}")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
LGTM exception in subject bpf_session_cookie() should be bpf_session_is_return().
Acked-by: Yonghong Song <yonghong.song@linux.dev>
prev parent reply other threads:[~2026-05-19 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 9:06 [PATCH] bpf: make bpf_session_cookie() reference optional Arnd Bergmann
2026-05-15 9:43 ` bot+bpf-ci
2026-05-19 16:18 ` Yonghong Song [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=18a7fe5f-427e-44b8-9e88-b82591e1d2b7@linux.dev \
--to=yonghong.song@linux.dev \
--cc=a.s.protopopov@gmail.com \
--cc=andrii@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=menglong8.dong@gmail.com \
--cc=puranjay@kernel.org \
--cc=song@kernel.org \
--cc=yatsenko@meta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox