From: Jiri Olsa <olsajiri@gmail.com>
To: SeongJae Park <sj@kernel.org>
Cc: martin.lau@linux.dev, ast@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexander Egorenkov <Alexander.Egorenkov@ibm.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] btf: warn but return no error for NULL btf from __register_btf_kfunc_id_set()
Date: Tue, 27 Jun 2023 18:20:39 +0200 [thread overview]
Message-ID: <ZJsMVxGVCJoF19wQ@krava> (raw)
In-Reply-To: <20230626181120.7086-1-sj@kernel.org>
On Mon, Jun 26, 2023 at 06:11:20PM +0000, SeongJae Park wrote:
> __register_btf_kfunc_id_set() assumes .BTF to be part of the module's
> .ko file if CONFIG_DEBUG_INFO_BTF is enabled. If that's not the case,
> the function prints an error message and return an error. As a result,
> such modules cannot be loaded.
>
> However, the section could be stripped out during a build process. It
> would be better to let the modules loaded, because their basic
> functionalities have no problem[1], though the BTF functionalities will
> not be supported. Make the function to lower the level of the message
> from error to warn, and return no error.
>
> [1] https://lore.kernel.org/bpf/20220219082037.ow2kbq5brktf4f2u@apollo.legion/
>
> Reported-by: Alexander Egorenkov <Alexander.Egorenkov@ibm.com>
> Link: https://lore.kernel.org/bpf/87y228q66f.fsf@oc8242746057.ibm.com/
> Suggested-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
> Link: https://lore.kernel.org/bpf/20220219082037.ow2kbq5brktf4f2u@apollo.legion/
> Fixes: dee872e124e8 ("bpf: Populate kfunc BTF ID sets in struct btf")
should it be this one in Fixes instead?
c446fdacb10d bpf: fix register_btf_kfunc_id_set for !CONFIG_DEBUG_INFO_BTF
other than that looks good
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
> Cc: <stable@vger.kernel.org> # 5.17.x
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
> kernel/bpf/btf.c | 12 ++++--------
> 1 file changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/bpf/btf.c b/kernel/bpf/btf.c
> index 6b682b8e4b50..d683f034996f 100644
> --- a/kernel/bpf/btf.c
> +++ b/kernel/bpf/btf.c
> @@ -7848,14 +7848,10 @@ static int __register_btf_kfunc_id_set(enum btf_kfunc_hook hook,
>
> btf = btf_get_module_btf(kset->owner);
> if (!btf) {
> - if (!kset->owner && IS_ENABLED(CONFIG_DEBUG_INFO_BTF)) {
> - pr_err("missing vmlinux BTF, cannot register kfuncs\n");
> - return -ENOENT;
> - }
> - if (kset->owner && IS_ENABLED(CONFIG_DEBUG_INFO_BTF_MODULES)) {
> - pr_err("missing module BTF, cannot register kfuncs\n");
> - return -ENOENT;
> - }
> + if (!kset->owner && IS_ENABLED(CONFIG_DEBUG_INFO_BTF))
> + pr_warn("missing vmlinux BTF, cannot register kfuncs\n");
> + if (kset->owner && IS_ENABLED(CONFIG_DEBUG_INFO_BTF_MODULES))
> + pr_warn("missing module BTF, cannot register kfuncs\n");
> return 0;
> }
> if (IS_ERR(btf))
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2023-06-27 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 18:11 [PATCH] btf: warn but return no error for NULL btf from __register_btf_kfunc_id_set() SeongJae Park
2023-06-27 16:20 ` Jiri Olsa [this message]
2023-06-27 16:37 ` SeongJae Park
2023-06-27 16:44 ` SeongJae Park
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=ZJsMVxGVCJoF19wQ@krava \
--to=olsajiri@gmail.com \
--cc=Alexander.Egorenkov@ibm.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sj@kernel.org \
--cc=stable@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 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.