[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pljz4b42.fsf@kloenk.dev>
Date: Mon, 03 Feb 2025 10:43:25 +0100
From: Fiona Behrens <me@...enk.dev>
To: Asahi Lina <lina@...hilina.net>
Cc: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn
Roy Baron <bjorn3_gh@...tonmail.com>, Benno Lossin
<benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Jann Horn <jannh@...gle.com>, Matthew Wilcox <willy@...radead.org>,
Paolo Bonzini <pbonzini@...hat.com>, Danilo Krummrich <dakr@...nel.org>,
Wedson Almeida Filho <wedsonaf@...il.com>, Valentin Obst
<kernel@...entinobst.de>, Andrew Morton <akpm@...ux-foundation.org>,
linux-mm@...ck.org, airlied@...hat.com, Abdiel Janulgue
<abdiel.janulgue@...il.com>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, asahi@...ts.linux.dev
Subject: Re: [PATCH 3/6] rust: page: Make with_page_mapped() and
with_pointer_into_page() public
Asahi Lina <lina@...hilina.net> writes:
> Lets users do (unsafe) complex page read/write operations without having
> to repeatedly call into read_raw()/write_raw() (which may be expensive
> in some cases).
>
> The functions themselves are not unsafe, but they do take a closure that
> receives a raw pointer, so actually making the access requires unsafe
> code.
>
> Signed-off-by: Asahi Lina <lina@...hilina.net>
Reviewed-by: Fiona Behrens <me@...enk.dev>
Powered by blists - more mailing lists