From: Fushuai Wang <fushuai.wang@linux.dev>
To: aliceryhl@google.com
Cc: akpm@linux-foundation.org, bp@alien8.de, brauner@kernel.org,
cyphar@cyphar.com, dave.hansen@linux.intel.com,
fushuai.wang@linux.dev, hpa@zytor.com, jack@suse.cz,
kees@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, luto@kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
mingo@redhat.com, peterz@infradead.org, rostedt@goodmis.org,
tglx@kernel.org, vmalik@redhat.com, wangfushuai@baidu.com,
x86@kernel.org, yury.norov@gmail.com
Subject: Re: [PATCH v2 1/6] uaccess: Add copy_from_user_nul helper
Date: Mon, 12 Jan 2026 18:00:59 +0800 [thread overview]
Message-ID: <20260112100059.12139-1-fushuai.wang@linux.dev> (raw)
In-Reply-To: <aWS9nOj4MAa7pYmS@google.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 999 bytes --]
>> From: Fushuai Wang <wangfushuai@baidu.com>
>>
>> Many places call copy_from_user() to copy a buffer from user space,
>> and then manually add a NULL terminator to the destination buffer,
>> e.g.:
>>
>> if (copy_from_user(dest, src, len))
>> return -EFAULT;
>> dest[len] = '\0';
>>
>> This is repetitive and error-prone. Add a copy_from_user_nul() helper to
>> simplify such patterns. It copied n bytes from user space to kernel space,
>> and NUL-terminates the destination buffer.
>>
>> Signed-off-by: Fushuai Wang <wangfushuai@baidu.com>
>
> Hmm, this function is very very similar to strncpy_from_user(). Should
> they be using that instead?
>
> Alice
The strncpy_from_user() is for NUL-terminated strings and stops at the
first NUL in userspace. But copy_from_user_nul() always copies a fixed length
and adds a NUL at the end in kernel space, even if userspace data doesn’t
contain a NUL.
So I think they are for different cases and can’t replace each other.
---
Regards,
WANG
next prev parent reply other threads:[~2026-01-12 10:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 7:30 [PATCH v2 0/6] uaccess: Introduce copy_from_user_nul helper Fushuai Wang
2026-01-12 7:30 ` [PATCH v2 1/6] uaccess: Add " Fushuai Wang
2026-01-12 9:23 ` Alice Ryhl
2026-01-12 10:00 ` Fushuai Wang [this message]
2026-01-12 11:20 ` Alice Ryhl
2026-01-12 12:22 ` Fushuai Wang
2026-01-12 13:22 ` Borislav Petkov
2026-01-12 15:40 ` Alice Ryhl
2026-01-12 16:28 ` Steven Rostedt
2026-01-12 16:37 ` Alice Ryhl
2026-01-13 18:00 ` Yury Norov
2026-01-13 18:17 ` Yury Norov
2026-01-16 8:42 ` Fushuai Wang
2026-01-12 7:30 ` [PATCH v2 2/6] x86/tlb: Use copy_from_user_nul() instead of copy_from_user() Fushuai Wang
2026-01-12 7:30 ` [PATCH v2 3/6] tracing: " Fushuai Wang
2026-01-12 15:43 ` Steven Rostedt
2026-01-13 17:05 ` Yury Norov
2026-01-13 18:03 ` Steven Rostedt
2026-01-12 7:30 ` [PATCH v2 4/6] userns: " Fushuai Wang
2026-01-12 7:30 ` [PATCH v2 5/6] time: " Fushuai Wang
2026-01-12 7:30 ` [PATCH v2 6/6] kstrtox: " Fushuai Wang
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=20260112100059.12139-1-fushuai.wang@linux.dev \
--to=fushuai.wang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=cyphar@cyphar.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@kernel.org \
--cc=vmalik@redhat.com \
--cc=wangfushuai@baidu.com \
--cc=x86@kernel.org \
--cc=yury.norov@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