From: Jiri Olsa <olsajiri@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
Christian Brauner <brauner@kernel.org>, bpf <bpf@vger.kernel.org>,
Saket Kumar Bhaskar <skb99@linux.ibm.com>,
Abhishek Dubey <adubey@linux.ibm.com>,
Hari Bathini <hbathini@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Subject: Re: [linux-next-20260327]resolve_btfids warnings for unresolved bpf_lsm_bdev_* symbols
Date: Mon, 30 Mar 2026 21:55:21 +0200 [thread overview]
Message-ID: <acrVKUy_EPiFFmV9@krava> (raw)
In-Reply-To: <CAADnVQ+KpCZqjAhMBzDZqm14yaORK-PG2VHRnub1Q0gYTHKG=Q@mail.gmail.com>
On Mon, Mar 30, 2026 at 07:42:18AM -0700, Alexei Starovoitov wrote:
> On Mon, Mar 30, 2026 at 6:45 AM Venkat Rao Bagalkote
> <venkat88@linux.ibm.com> wrote:
> >
> > Hi,
> >
> >
> > While testing linux-next, I’m seeing the following warnings during the
> > build:
> >
> >
> > WARN: resolve_btfids: unresolved symbol bpf_lsm_bdev_free
> >
> > WARN: resolve_btfids: unresolved symbol bpf_lsm_bdev_alloc
> >
>
> Christian,
>
> looks like those two need some #ifdef
>
I think it's wrong hooks name, this fixes it for me
jirka
---
diff --git a/kernel/bpf/bpf_lsm.c b/kernel/bpf/bpf_lsm.c
index 119e3942cf5a..0e74325d96a6 100644
--- a/kernel/bpf/bpf_lsm.c
+++ b/kernel/bpf/bpf_lsm.c
@@ -383,7 +383,7 @@ BTF_ID(func, bpf_lsm_task_prctl)
BTF_ID(func, bpf_lsm_task_setscheduler)
BTF_ID(func, bpf_lsm_task_to_inode)
BTF_ID(func, bpf_lsm_userns_create)
-BTF_ID(func, bpf_lsm_bdev_alloc)
+BTF_ID(func, bpf_lsm_bdev_alloc_security)
BTF_ID(func, bpf_lsm_bdev_setintegrity)
BTF_SET_END(sleepable_lsm_hooks)
@@ -397,8 +397,8 @@ BTF_ID(func, bpf_lsm_sk_alloc_security)
BTF_ID(func, bpf_lsm_sk_free_security)
#endif /* CONFIG_SECURITY_NETWORK */
BTF_ID(func, bpf_lsm_task_free)
-BTF_ID(func, bpf_lsm_bdev_alloc)
-BTF_ID(func, bpf_lsm_bdev_free)
+BTF_ID(func, bpf_lsm_bdev_alloc_security)
+BTF_ID(func, bpf_lsm_bdev_free_security)
BTF_SET_END(untrusted_lsm_hooks)
bool bpf_lsm_is_sleepable_hook(u32 btf_id)
next prev parent reply other threads:[~2026-03-30 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 13:34 [linux-next-20260327]resolve_btfids warnings for unresolved bpf_lsm_bdev_* symbols Venkat Rao Bagalkote
2026-03-30 14:42 ` Alexei Starovoitov
2026-03-30 19:55 ` Jiri Olsa [this message]
2026-03-31 7:55 ` Christian Brauner
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=acrVKUy_EPiFFmV9@krava \
--to=olsajiri@gmail.com \
--cc=adubey@linux.ibm.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=maddy@linux.ibm.com \
--cc=skb99@linux.ibm.com \
--cc=venkat88@linux.ibm.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