From: Rong Tao <rtoax@foxmail.com>
To: Viktor Malik <vmalik@redhat.com>, andrii@kernel.org, ast@kernel.org
Cc: Rong Tao <rongtao@cestc.cn>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>,
"open list:BPF [GENERAL] (Safe Dynamic Programs and Tools)"
<bpf@vger.kernel.org>, open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH bpf-next 1/2] bpf: add bpf_strcasecmp kfunc
Date: Tue, 2 Sep 2025 15:14:43 +0800 [thread overview]
Message-ID: <tencent_AC7510F30CC28482B2982E5155905F634609@qq.com> (raw)
In-Reply-To: <f0194235-19ae-43de-b73d-b2d8b7f77035@redhat.com>
On 9/2/25 15:08, Viktor Malik wrote:
> On 9/2/25 08:17, Rong Tao wrote:
>> From: Rong Tao <rongtao@cestc.cn>
>>
>> bpf_strcasecmp() function performs same like bpf_strcmp() except ignoring
>> the case of the characters.
>>
>> Signed-off-by: Rong Tao <rongtao@cestc.cn>
>> ---
>> kernel/bpf/helpers.c | 56 +++++++++++++++++++++++++++++++++-----------
>> 1 file changed, 42 insertions(+), 14 deletions(-)
>>
>> diff --git a/kernel/bpf/helpers.c b/kernel/bpf/helpers.c
>> index 401b4932cc49..e807a708e5fc 100644
>> --- a/kernel/bpf/helpers.c
>> +++ b/kernel/bpf/helpers.c
>> @@ -3349,20 +3349,7 @@ __bpf_kfunc void __bpf_trap(void)
>> * __get_kernel_nofault instead of plain dereference to make them safe.
>> */
>>
>> -/**
>> - * bpf_strcmp - Compare two strings
>> - * @s1__ign: One string
>> - * @s2__ign: Another string
>> - *
>> - * Return:
>> - * * %0 - Strings are equal
>> - * * %-1 - @s1__ign is smaller
>> - * * %1 - @s2__ign is smaller
>> - * * %-EFAULT - Cannot read one of the strings
>> - * * %-E2BIG - One of strings is too large
>> - * * %-ERANGE - One of strings is outside of kernel address space
>> - */
>> -__bpf_kfunc int bpf_strcmp(const char *s1__ign, const char *s2__ign)
>> +int __bpf_strcasecmp(const char *s1__ign, const char *s2__ign, bool ignore_case)
> No need to use the `__ign` suffix here.
Viktor, Thanks for your review, i'll submit v2 soon.
Rong Tao
>
> Otherwise LGTM. I guess that it could be useful in some applications.
>
> Viktor
>
>> {
>> char c1, c2;
>> int i;
>> @@ -3376,6 +3363,10 @@ __bpf_kfunc int bpf_strcmp(const char *s1__ign, const char *s2__ign)
>> for (i = 0; i < XATTR_SIZE_MAX; i++) {
>> __get_kernel_nofault(&c1, s1__ign, char, err_out);
>> __get_kernel_nofault(&c2, s2__ign, char, err_out);
>> + if (ignore_case) {
>> + c1 = tolower(c1);
>> + c2 = tolower(c2);
>> + }
>> if (c1 != c2)
>> return c1 < c2 ? -1 : 1;
>> if (c1 == '\0')
>> @@ -3388,6 +3379,42 @@ __bpf_kfunc int bpf_strcmp(const char *s1__ign, const char *s2__ign)
>> return -EFAULT;
>> }
>>
>> +/**
>> + * bpf_strcmp - Compare two strings
>> + * @s1__ign: One string
>> + * @s2__ign: Another string
>> + *
>> + * Return:
>> + * * %0 - Strings are equal
>> + * * %-1 - @s1__ign is smaller
>> + * * %1 - @s2__ign is smaller
>> + * * %-EFAULT - Cannot read one of the strings
>> + * * %-E2BIG - One of strings is too large
>> + * * %-ERANGE - One of strings is outside of kernel address space
>> + */
>> +__bpf_kfunc int bpf_strcmp(const char *s1__ign, const char *s2__ign)
>> +{
>> + return __bpf_strcasecmp(s1__ign, s2__ign, false);
>> +}
>> +
>> +/**
>> + * bpf_strcasecmp - Compare two strings, ignoring the case of the characters
>> + * @s1__ign: One string
>> + * @s2__ign: Another string
>> + *
>> + * Return:
>> + * * %0 - Strings are equal
>> + * * %-1 - @s1__ign is smaller
>> + * * %1 - @s2__ign is smaller
>> + * * %-EFAULT - Cannot read one of the strings
>> + * * %-E2BIG - One of strings is too large
>> + * * %-ERANGE - One of strings is outside of kernel address space
>> + */
>> +__bpf_kfunc int bpf_strcasecmp(const char *s1__ign, const char *s2__ign)
>> +{
>> + return __bpf_strcasecmp(s1__ign, s2__ign, true);
>> +}
>> +
>> /**
>> * bpf_strnchr - Find a character in a length limited string
>> * @s__ign: The string to be searched
>> @@ -3832,6 +3859,7 @@ BTF_ID_FLAGS(func, bpf_iter_dmabuf_destroy, KF_ITER_DESTROY | KF_SLEEPABLE)
>> #endif
>> BTF_ID_FLAGS(func, __bpf_trap)
>> BTF_ID_FLAGS(func, bpf_strcmp);
>> +BTF_ID_FLAGS(func, bpf_strcasecmp);
>> BTF_ID_FLAGS(func, bpf_strchr);
>> BTF_ID_FLAGS(func, bpf_strchrnul);
>> BTF_ID_FLAGS(func, bpf_strnchr);
next prev parent reply other threads:[~2025-09-02 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1756793624.git.rongtao@cestc.cn>
2025-09-02 6:17 ` Rong Tao
2025-09-02 7:08 ` Viktor Malik
2025-09-02 7:14 ` Rong Tao [this message]
2025-09-02 6:18 ` [PATCH bpf-next 2/2] selftests/bpf: Test kfunc bpf_strcasecmp Rong Tao
2025-09-02 7:12 ` Viktor Malik
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=tencent_AC7510F30CC28482B2982E5155905F634609@qq.com \
--to=rtoax@foxmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=rongtao@cestc.cn \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=vmalik@redhat.com \
--cc=yonghong.song@linux.dev \
/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
all inboxes | Powered by JetHome®