From: Tao Chen <chen.dylane@linux.dev>
To: Yonghong Song <yonghong.song@linux.dev>,
ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Clean code with bpf_copy_to_user
Date: Fri, 4 Jul 2025 00:19:33 +0800 [thread overview]
Message-ID: <9f92515f-6dad-4ff6-884e-e60016e36ae7@linux.dev> (raw)
In-Reply-To: <d9c78add-d2e0-4d7c-a5a3-2355417cf9a6@linux.dev>
在 2025/7/4 00:14, Yonghong Song 写道:
>
>
> On 7/3/25 9:03 AM, Tao Chen wrote:
>> 在 2025/7/3 23:35, Yonghong Song 写道:
>>>
>>>
>>> On 7/3/25 5:43 AM, Tao Chen wrote:
>>>> No logic change, just use bpf_copy_to_user to clean code.
>>>>
>>>> Signed-off-by: Tao Chen <chen.dylane@linux.dev>
>>>> ---
>>>> kernel/bpf/syscall.c | 17 +++--------------
>>>> 1 file changed, 3 insertions(+), 14 deletions(-)
>>>>
>>>> diff --git a/kernel/bpf/syscall.c b/kernel/bpf/syscall.c
>>>> index e6eea594f1c..ca152d36312 100644
>>>> --- a/kernel/bpf/syscall.c
>>>> +++ b/kernel/bpf/syscall.c
>>>> @@ -5208,21 +5208,10 @@ static int bpf_task_fd_query_copy(const
>>>> union bpf_attr *attr,
>>>> if (put_user(zero, ubuf))
>>>> return -EFAULT;
>>>> - } else if (input_len >= len + 1) {
>>>> - /* ubuf can hold the string with NULL terminator */
>>>> - if (copy_to_user(ubuf, buf, len + 1))
>>>> - return -EFAULT;
>>>> } else {
>>>> - /* ubuf cannot hold the string with NULL terminator,
>>>> - * do a partial copy with NULL terminator.
>>>> - */
>>>> - char zero = '\0';
>>>> -
>>>> - err = -ENOSPC;
>>>> - if (copy_to_user(ubuf, buf, input_len - 1))
>>>> - return -EFAULT;
>>>> - if (put_user(zero, ubuf + input_len - 1))
>>>> - return -EFAULT;
>>>> + err = bpf_copy_to_user(ubuf, buf, input_len, len);
>>>> + if (err)
>>>> + return err;
>>>> }
>>>> }
>>>
>>> Actually, there is a return value change with this patch.
>>> bpf_copy_to_user() return returns -ENOSPC while the original
>>> implementation may return -EFAULT due to following code.
>>>
>>> if (put_user(prog_id, &uattr->task_fd_query.prog_id) ||
>>> put_user(fd_type, &uattr->task_fd_query.fd_type) ||
>>> put_user(probe_offset, &uattr-
>>> >task_fd_query.probe_offset) ||
>>> put_user(probe_addr, &uattr->task_fd_query.probe_addr))
>>> return -EFAULT;
>>>
>>> return err;
>>>
>>
>> You are right, maybe we can just use:
>> err = bpf_copy_to_user(ubuf, buf, input_len, len);
>> and no return check
>> or move these put_user code to the front.
>
> Maybe do the following?
>
> err = bpf_copy_to_user(ubuf, buf, input_len, len);
> if (err && err != -ENOSPC)
> return err;
>
Well, it looks better, i will change it in v2, thanks.
--
Best Regards
Tao Chen
prev parent reply other threads:[~2025-07-03 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 12:43 Tao Chen
2025-07-03 15:35 ` Yonghong Song
2025-07-03 16:03 ` Tao Chen
2025-07-03 16:14 ` Yonghong Song
2025-07-03 16:19 ` Tao Chen [this message]
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=9f92515f-6dad-4ff6-884e-e60016e36ae7@linux.dev \
--to=chen.dylane@linux.dev \
--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=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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
Powered by JetHome