From: Viktor Malik <vmalik@redhat.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
linux-modules@vger.kernel.org,
Nick Alcock <nick.alcock@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejun Heo <tj@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH bpf-next v10 1/2] bpf: Fix attaching fentry/fexit/fmod_ret/lsm to modules
Date: Mon, 13 Mar 2023 08:16:30 +0100 [thread overview]
Message-ID: <70b77670-43d5-ff38-abfe-3379cc54a82e@redhat.com> (raw)
In-Reply-To: <ZAuB/cnEsPt0f0vb@bombadil.infradead.org>
On 3/10/23 20:16, Luis Chamberlain wrote:
> Please add linux-modules in the future. My review below.
Sorry for missing that, I'll add it next time.
>
> On Fri, Mar 10, 2023 at 08:40:59AM +0100, Viktor Malik wrote:
[snip]
> My review of the critical part below.
>
>> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
>> index 45a082284464..3905bb20b9a1 100644
>> --- a/kernel/bpf/verifier.c
>> +++ b/kernel/bpf/verifier.c
>> @@ -18432,8 +18434,17 @@ int bpf_check_attach_target(struct bpf_verifier_log *log,
>> else
>> addr = (long) tgt_prog->aux->func[subprog]->bpf_func;
>> } else {
>> - addr = kallsyms_lookup_name(tname);
>> + if (btf_is_module(btf)) {
>> + mod = btf_try_get_module(btf);
>> + if (mod)
>> + addr = find_kallsyms_symbol_value(mod, tname);
>> + else
>> + addr = 0;
>> + } else {
>> + addr = kallsyms_lookup_name(tname);
>> + }
>> if (!addr) {
>> + module_put(mod);
>> bpf_log(log,
>> "The address of function %s cannot be found\n",
>> tname);
>
> If btf_modules linked list is ensured to not remove the btf module
> during this operation, sure this is safe, as per the new guidelines I've
> posted for try_module_get() this seems to be using try_module_get()
> using the implied protection.
I believe that is the case. btf_try_get_module checks the
BTF_F_MODULE_LIVE flag before calling try_module_get and the flag is set
only when the module notifier callback is called with MODULE_STATE_LIVE.
In addition, all BTF module operations are called under the same mutex,
so the module cannot be removed in-between.
>
> Please review the docs. *If* it respects that usage then feel free to
> add:
>
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Thanks for the review. Unless there are more change requests, I'll leave
it up to the maintainers to add the tag.
Viktor
>
> Luis
>
next prev parent reply other threads:[~2023-03-13 7:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 7:40 [PATCH bpf-next v10 0/2] Fix attaching fentry/fexit/fmod_ret/lsm to modules Viktor Malik
2023-03-10 7:40 ` [PATCH bpf-next v10 1/2] bpf: " Viktor Malik
2023-03-10 19:16 ` Luis Chamberlain
2023-03-13 7:16 ` Viktor Malik [this message]
2023-03-16 1:32 ` kernel test robot
2023-03-16 1:34 ` Alexei Starovoitov
2023-03-16 1:39 ` Alexei Starovoitov
2023-03-16 7:37 ` Viktor Malik
2023-03-10 7:41 ` [PATCH bpf-next v10 2/2] bpf/selftests: Test fentry attachment to shadowed functions Viktor Malik
2023-03-15 19:50 ` [PATCH bpf-next v10 0/2] Fix attaching fentry/fexit/fmod_ret/lsm to modules patchwork-bot+netdevbpf
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=70b77670-43d5-ff38-abfe-3379cc54a82e@redhat.com \
--to=vmalik@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gregkh@linuxfoundation.org \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=keescook@chromium.org \
--cc=kpsingh@kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mcgrof@kernel.org \
--cc=nick.alcock@oracle.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=yhs@fb.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