From: Kari Argillander <kari.argillander@gmail.com>
To: Dirk Behme <dirk.behme@gmail.com>
Cc: "Gary Guo" <gary@garyguo.net>,
"Alice Ryhl" <aliceryhl@google.com>,
"Dirk Behme" <dirk.behme@de.bosch.com>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
linux-mm@kvack.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rust: page: Simplify overflow check using checked_add()
Date: Tue, 23 Dec 2025 14:50:46 +0200 [thread overview]
Message-ID: <CAC=eVgQBrfcWSgmLAqL-RqQr8FrcCS0e1j4aQ-ck5dBSJt4zNA@mail.gmail.com> (raw)
In-Reply-To: <46e188a4-4b74-4206-ba18-f107f45bb98d@gmail.com>
On 23.12.2025 14.29 +0200 Dirk Behme (dirk.behme@gmail.com) wrote:
>
> On 23.12.25 12:57, Gary Guo wrote:
> > On Tue, 23 Dec 2025 12:06:17 +0200
> > Kari Argillander <kari.argillander@gmail.com> wrote:
> >
> >> Replace the explicit bounds comparisons with a single checked_add()-based
> >> range check. This avoids redundant comparisons, makes the overflow case
> >> explicit, and results in simpler generated code (checked with godbolt
> >> for x86).
> >>
> >> No functional change intended.
> >>
> >> Reviewed-by: Dirk Behme <dirk.behme@de.bosch.com>
> >> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
> >> Signed-off-by: Kari Argillander <kari.argillander@gmail.com>
> >> ---
> >> Changes in v2:
> >> - Added MSVR todo (Dirk Behme)
> >> - Link to v1: https://lore.kernel.org/r/20251219-rust-page-check-v1-1-df2e52fa3bd5@gmail.com
> >> ---
> >> rust/kernel/page.rs | 19 +++++++++----------
> >> 1 file changed, 9 insertions(+), 10 deletions(-)
> >>
> >> diff --git a/rust/kernel/page.rs b/rust/kernel/page.rs
> >> index 432fc0297d4a..cd2af7e4c357 100644
> >> --- a/rust/kernel/page.rs
> >> +++ b/rust/kernel/page.rs
> >> @@ -239,17 +239,16 @@ fn with_pointer_into_page<T>(
> >> len: usize,
> >> f: impl FnOnce(*mut u8) -> Result<T>,
> >> ) -> Result<T> {
> >> - let bounds_ok = off <= PAGE_SIZE && len <= PAGE_SIZE && (off + len) <= PAGE_SIZE;
> >> -
> >> - if bounds_ok {
> >> - self.with_page_mapped(move |page_addr| {
> >> - // SAFETY: The `off` integer is at most `PAGE_SIZE`, so this pointer offset will
> >> - // result in a pointer that is in bounds or one off the end of the page.
> >> - f(unsafe { page_addr.add(off) })
> >> - })
> >> - } else {
> >> - Err(EINVAL)
> >> + // TODO: Replace `map_or` with `is_none_or` once the MSRV is >= 1.82.
> >
> > I was about to suggest just enable the feature gate, but turns out it was
> > only added in 1.81. That's a fast one to stabilize!
>
>
> With Alexandre's `matches!` proposal I was thinking that we could drop
> the TODO comment and we won't need to touch this file again once MSRV
> is >= 1.82. Opinions?
Personally I like `is_none_or` more than `matches!` but then thinking again I
agree that it might be better because we do not have to leave TODO here. I will
respin again tomorrow.
I also checked that output for at least x86 is identical.
> Cheers
>
> Dirk
>
>
> > Reviewed-by: Gary Guo <gary@garyguo.net>
> >
> > Best,
> > Gary
> >
> >> + if off.checked_add(len).map_or(true, |end| end > PAGE_SIZE) {
> >> + return Err(EINVAL);
> >> }
> >> +
> >> + self.with_page_mapped(move |page_addr| {
> >> + // SAFETY: The `off` integer is at most `PAGE_SIZE`, so this pointer offset will
> >> + // result in a pointer that is in bounds or one off the end of the page.
> >> + f(unsafe { page_addr.add(off) })
> >> + })
> >> }
> >>
> >> /// Maps the page and reads from it into the given buffer.
> >>
> >> ---
> >> base-commit: cc3aa43b44bdb43dfbac0fcb51c56594a11338a8
> >> change-id: 20251219-rust-page-check-819ccc39c53a
> >>
> >> Best regards,
> >
> >
>
prev parent reply other threads:[~2025-12-23 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 10:06 Kari Argillander
2025-12-23 11:57 ` Gary Guo
2025-12-23 12:29 ` Dirk Behme
2025-12-23 12:50 ` Gary Guo
2025-12-23 12:50 ` Kari Argillander [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='CAC=eVgQBrfcWSgmLAqL-RqQr8FrcCS0e1j4aQ-ck5dBSJt4zNA@mail.gmail.com' \
--to=kari.argillander@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=dirk.behme@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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