From: Danilo Krummrich <dakr@kernel.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] uaccess: rust: add UserSliceReader::strcpy_into_buf
Date: Mon, 5 May 2025 18:22:31 +0200 [thread overview]
Message-ID: <aBjlx_AfQCS-pmht@polis> (raw)
In-Reply-To: <20250505-strncpy-from-user-v3-2-85c677fd4f91@google.com>
On Mon, May 05, 2025 at 12:17:32PM +0000, Alice Ryhl wrote:
> + /// Read a NUL-terminated string from userspace and return it.
> + ///
> + /// The string is read into `buf` and a NUL-terminator is added if the end of `buf` is reached.
> + /// Since there must be space to add a NUL-terminator, the buffer must not be empty. The
> + /// returned `&CStr` points into `buf`.
> + ///
> + /// Fails with [`EFAULT`] if the read happens on a bad address (some data may have been
> + /// copied).
> + #[doc(alias = "strncpy_from_user")]
> + pub fn strcpy_into_buf<'buf>(self, buf: &'buf mut [u8]) -> Result<&'buf CStr> {
> + if buf.is_empty() {
> + return Err(EINVAL);
> + }
> +
> + // SAFETY: The types are compatible and `strncpy_from_user` doesn't write uninitialized
> + // bytes to `buf`.
> + let mut dst = unsafe { &mut *(buf as *mut [u8] as *mut [MaybeUninit<u8>]) };
> +
> + // We never read more than `self.length` bytes.
> + if dst.len() > self.length {
> + dst = &mut dst[..self.length];
> + }
> +
> + let mut len = raw_strncpy_from_user(self.ptr, dst)?;
> + if len < dst.len() {
> + // Add one to include the NUL-terminator.
> + len += 1;
> + } else if len < buf.len() {
> + // This implies that len == dst.len() < buf.len().
> + //
> + // This means that we could not fill the entire buffer, but we had to stop reading
> + // because we hit the `self.length` limit of this `UserSliceReader`. Since we did not
> + // fill the buffer, we treat this case as if we tried to read past the `self.length`
> + // limit and received a page fault, which is consistent with other `UserSliceReader`
> + // methods that also return page faults when you exceed `self.length`.
> + return Err(EFAULT);
> + } else {
> + // This implies that len == buf.len().
> + //
> + // This means that we filled the buffer exactly. In this case, we add a NUL-terminator
> + // and return it. Unlike the `len < dst.len()` branch, don't modify `len` because it
> + // already represents the length including the NUL-terminator.
> + //
> + // SAFETY: Due to the check at the beginning, the buffer is not empty.
> + unsafe { *buf.last_mut().unwrap_unchecked() = 0 };
> + }
> +
> + // SAFETY: `raw_strncpy_from_user` guarantees that this range of bytes represents a
> + // NUL-terminated string with the only NUL byte being at the end.
This isn't true if we hit the else case above, no?
With that fixed,
Reviewed-by: Danilo Krummrich <dakr@kernel.org>
next prev parent reply other threads:[~2025-05-05 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 12:17 [PATCH v3 0/2] strncpy_from_user for Rust Alice Ryhl
2025-05-05 12:17 ` [PATCH v3 1/2] uaccess: rust: add strncpy_from_user Alice Ryhl
2025-05-05 14:30 ` Greg Kroah-Hartman
2025-05-05 19:23 ` Boqun Feng
2025-05-06 9:18 ` Alice Ryhl
2025-05-06 12:52 ` Greg Kroah-Hartman
2025-05-06 13:30 ` Alice Ryhl
2025-05-05 12:17 ` [PATCH v3 2/2] uaccess: rust: add UserSliceReader::strcpy_into_buf Alice Ryhl
2025-05-05 16:22 ` Danilo Krummrich [this message]
2025-05-06 9:10 ` Alice Ryhl
2025-05-05 12:21 ` [PATCH v3 0/2] strncpy_from_user for Rust Alice Ryhl
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=aBjlx_AfQCS-pmht@polis \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=viro@zeniv.linux.org.uk \
/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