From: Alice Ryhl <aliceryhl@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Danilo Krummrich" <kernel@dakr.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"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>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] uaccess: rust: add UserSliceReader::strcpy_into_buf
Date: Tue, 29 Apr 2025 15:15:01 +0000 [thread overview]
Message-ID: <aBDs9aMQSCLIqD96@google.com> (raw)
In-Reply-To: <2025042946-accustom-bankroll-d934@gregkh>
On Tue, Apr 29, 2025 at 01:48:19PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 29, 2025 at 01:38:26PM +0200, Danilo Krummrich wrote:
> > On 2025-04-29 13:09, Greg Kroah-Hartman wrote:
> > > On Tue, Apr 29, 2025 at 09:02:23AM +0000, Alice Ryhl wrote:
> > > > + 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() {
> > > > + // We hit the `self.length` limit before `buf.len()`.
> > > > + return Err(EFAULT);
> > >
> > > How can this happen?
> >
> > See my reply here (if I did not get it wrong):
> >
> > https://lore.kernel.org/rust-for-linux/aBCrqJe4two4I45G@pollux/
>
> Ah, I should have read ahead :)
>
> I agree, some comments here would be good. We want everyone to be able
> to easily read and understand this code, off-by-one errors are rough.
I will add this comment:
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);
Alice
next prev parent reply other threads:[~2025-04-29 15:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 9:02 [PATCH v2 0/2] strncpy_from_user for Rust Alice Ryhl
2025-04-29 9:02 ` [PATCH v2 1/2] uaccess: rust: add strncpy_from_user Alice Ryhl
2025-04-29 10:11 ` Danilo Krummrich
2025-04-29 10:30 ` Alice Ryhl
2025-04-29 11:04 ` Greg Kroah-Hartman
2025-04-29 15:09 ` Alice Ryhl
2025-04-29 17:30 ` Boqun Feng
2025-04-29 20:28 ` John Hubbard
2025-04-29 20:31 ` Boqun Feng
2025-04-29 9:02 ` [PATCH v2 2/2] uaccess: rust: add UserSliceReader::strcpy_into_buf Alice Ryhl
2025-04-29 10:36 ` Danilo Krummrich
2025-04-29 11:09 ` Greg Kroah-Hartman
2025-04-29 11:38 ` Danilo Krummrich
2025-04-29 11:48 ` Greg Kroah-Hartman
2025-04-29 15:15 ` Alice Ryhl [this message]
2025-04-29 15:50 ` Greg Kroah-Hartman
2025-04-30 10:58 ` Alice Ryhl
2025-04-30 11:04 ` Greg Kroah-Hartman
2025-04-29 18:02 ` Boqun Feng
2025-04-29 18:26 ` Boqun Feng
2025-04-29 19:29 ` Alice Ryhl
2025-04-29 19:47 ` Boqun Feng
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=aBDs9aMQSCLIqD96@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@dakr.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