From: Kui-Feng Lee <sinquersw@gmail.com>
To: Martin KaFai Lau <martin.lau@linux.dev>, thinker.li@gmail.com
Cc: kuifeng@meta.com, bpf@vger.kernel.org, ast@kernel.org,
song@kernel.org, kernel-team@meta.com, andrii@kernel.org
Subject: Re: [PATCH bpf-next] bpf: Check cfi_stubs before registering a struct_ops type.
Date: Thu, 15 Feb 2024 11:19:24 -0800 [thread overview]
Message-ID: <6b75ba79-dfc8-4681-b8d5-3f63e0b6706a@gmail.com> (raw)
In-Reply-To: <32dd0715-1f36-4de2-ab69-0e21019eade5@linux.dev>
On 2/15/24 10:23, Martin KaFai Lau wrote:
> On 2/14/24 6:24 PM, thinker.li@gmail.com wrote:
>> From: Kui-Feng Lee <thinker.li@gmail.com>
>>
>> Recently, cfi_stubs were introduced. However, existing struct_ops types
>> that are not in the upstream may not be aware of this, resulting in
>> kernel
>> crashes. By rejecting struct_ops types that do not provide cfi_stubs
>> during
>> registration, these crashes can be avoided.
>>
>> Signed-off-by: Kui-Feng Lee <thinker.li@gmail.com>
>> ---
>> kernel/bpf/bpf_struct_ops.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/kernel/bpf/bpf_struct_ops.c b/kernel/bpf/bpf_struct_ops.c
>> index 0d7be97a2411..e35958142dce 100644
>> --- a/kernel/bpf/bpf_struct_ops.c
>> +++ b/kernel/bpf/bpf_struct_ops.c
>> @@ -302,6 +302,11 @@ int bpf_struct_ops_desc_init(struct
>> bpf_struct_ops_desc *st_ops_desc,
>> }
>> sprintf(value_name, "%s%s", VALUE_PREFIX, st_ops->name);
>> + if (!st_ops->cfi_stubs) {
>
> How about *(void **)(st_ops->cfi_stubs + moff) ? Does it need a NULL check?
This NULL check is necessary to prevent the crash but good to have.
>
> Please add a test.
Got it!
>
>> + pr_warn("The struct_ops %s has no cfi_stubs\n", st_ops->name);
>> + return -EINVAL;
>> + }
>> +
>> type_id = btf_find_by_name_kind(btf, st_ops->name,
>> BTF_KIND_STRUCT);
>> if (type_id < 0) {
>
next prev parent reply other threads:[~2024-02-15 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 2:24 [PATCH bpf-next] bpf: Check cfi_stubs before registering a struct_ops type thinker.li
2024-02-15 18:23 ` Martin KaFai Lau
2024-02-15 19:19 ` Kui-Feng Lee [this message]
2024-02-15 19:20 ` Kui-Feng Lee
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=6b75ba79-dfc8-4681-b8d5-3f63e0b6706a@gmail.com \
--to=sinquersw@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
--cc=thinker.li@gmail.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