From: "Danilo Krummrich" <dakr@kernel.org>
To: "Alice Ryhl" <aliceryhl@google.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Arnd Bergmann" <arnd@arndb.de>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Matthew Maurer" <mmaurer@google.com>,
"Lee Jones" <lee@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Benno Lossin" <lossin@kernel.org>
Subject: Re: [PATCH v4 2/4] rust: iov: add iov_iter abstractions for ITER_DEST
Date: Wed, 13 Aug 2025 13:34:46 +0200 [thread overview]
Message-ID: <DC19O2AXINJW.3DS7GDDU3O3E1@kernel.org> (raw)
In-Reply-To: <20250813-iov-iter-v4-2-c4f1932b05ef@google.com>
On Wed Aug 13, 2025 at 10:27 AM CEST, Alice Ryhl wrote:
> + /// Write data to this IO vector.
> + ///
> + /// Returns the number of bytes that were written. If this is shorter than the provided slice,
> + /// then no more bytes can be written.
> + #[inline]
> + pub fn copy_to_iter(&mut self, input: &[u8]) -> usize {
> + // SAFETY:
> + // * By the struct invariants, it is still valid to write to this IO vector.
NIT: I think we usually say type invariants.
> + // * `input` is valid for `input.len()` bytes.
> + unsafe { bindings::_copy_to_iter(input.as_ptr().cast(), input.len(), self.as_raw()) }
> + }
> +
> + /// Utility for implementing `read_iter` given the full contents of the file.
> + ///
> + /// The full contents of the file being read from is represented by `contents`. This call will
> + /// write the appropriate sub-slice of `contents` and update the file position in `ppos` so
> + /// that the file will appear to contain `contents` even if takes multiple reads to read the
> + /// entire file.
> + #[inline]
> + pub fn simple_read_from_buffer(&mut self, ppos: &mut i64, contents: &[u8]) -> Result<usize> {
> + if *ppos < 0 {
> + return Err(EINVAL);
> + }
> + let Ok(pos) = usize::try_from(*ppos) else {
> + return Ok(0);
> + };
> + if pos >= contents.len() {
> + return Ok(0);
> + }
> +
> + // BOUNDS: We just checked that `pos < contents.len()` above.
I like this one (and the one below). It would be nice to have a lint asking for such
comments, such as I'd like to have a "FORGET" one. :)
> + let num_written = self.copy_to_iter(&contents[pos..]);
> +
> + // OVERFLOW: `pos+num_written <= contents.len() <= isize::MAX <= i64::MAX`.
> + *ppos = (pos + num_written) as i64;
> +
> + Ok(num_written)
> + }
> +}
Reviewed-by: Danilo Krummrich <dakr@kernel.org>
next prev parent reply other threads:[~2025-08-13 11:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 8:27 [PATCH v4 0/4] Rust support for `struct iov_iter` Alice Ryhl
2025-08-13 8:27 ` [PATCH v4 1/4] rust: iov: add iov_iter abstractions for ITER_SOURCE Alice Ryhl
2025-08-13 11:27 ` Danilo Krummrich
2025-08-13 11:40 ` Miguel Ojeda
2025-08-13 12:16 ` Alice Ryhl
2025-08-13 8:27 ` [PATCH v4 2/4] rust: iov: add iov_iter abstractions for ITER_DEST Alice Ryhl
2025-08-13 11:34 ` Danilo Krummrich [this message]
2025-08-13 13:33 ` Benoît du Garreau
2025-08-14 7:57 ` Alice Ryhl
2025-08-13 8:27 ` [PATCH v4 3/4] rust: miscdevice: Provide additional abstractions for iov_iter and kiocb structures Alice Ryhl
2025-08-13 11:39 ` Danilo Krummrich
2025-08-13 12:16 ` Alice Ryhl
2025-08-15 9:56 ` Andreas Hindborg
2025-08-13 8:27 ` [PATCH v4 4/4] samples: rust_misc_device: Expand the sample to support read()ing from userspace Alice Ryhl
2025-08-13 11:20 ` [PATCH v4 0/4] Rust support for `struct iov_iter` Danilo Krummrich
2025-08-19 9:03 ` 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=DC19O2AXINJW.3DS7GDDU3O3E1@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mmaurer@google.com \
--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;
as well as URLs for NNTP newsgroup(s).