From: Alice Ryhl <aliceryhl@google.com>
To: Tamir Duberstein <tamird@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"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 3/6] rust: arc: split unsafe block, add missing comment
Date: Fri, 8 Nov 2024 12:38:01 +0100 [thread overview]
Message-ID: <CAH5fLgiMHE5GXQv8pSR_KYWsa44zr1o_FNrg1mj8QuTvNQmXhQ@mail.gmail.com> (raw)
In-Reply-To: <20241104-borrow-mut-v2-3-de650678648d@gmail.com>
On Mon, Nov 4, 2024 at 10:20 PM Tamir Duberstein <tamird@gmail.com> wrote:
>
> The new SAFETY comment style is taken from existing comments in `deref`
> and `drop.
>
> Signed-off-by: Tamir Duberstein <tamird@gmail.com>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
> diff --git a/rust/kernel/sync/arc.rs b/rust/kernel/sync/arc.rs
> index af383bcd003e1122ebe1b62a49fe40279458e379..9adea755a5ad1a7b03f7fc30a7abc76c1f966c6c 100644
> --- a/rust/kernel/sync/arc.rs
> +++ b/rust/kernel/sync/arc.rs
> @@ -377,10 +377,14 @@ fn as_ref(&self) -> &T {
>
> impl<T: ?Sized> Clone for Arc<T> {
> fn clone(&self) -> Self {
> + // SAFETY: By the type invariant, there is necessarily a reference to the object, so it is
> + // safe to dereference it.
> + let refcount = unsafe { self.ptr.as_ref() }.refcount.get();
I would normally prefer to avoid creating a reference to the entire
ArcInner, but in this particular case it is okay due to the specifics
of how Arc works.
Alice
next prev parent reply other threads:[~2024-11-08 11:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 21:20 [PATCH v2 0/6] rust: add improved version of `ForeignOwnable::borrow_mut` Tamir Duberstein
2024-11-04 21:20 ` [PATCH v2 1/6] rust: arc: use `NonNull::new_unchecked` Tamir Duberstein
2024-11-04 21:20 ` [PATCH v2 2/6] rust: types: avoid `as` casts Tamir Duberstein
2024-11-08 11:35 ` Alice Ryhl
2024-11-08 12:22 ` Tamir Duberstein
2024-11-08 13:15 ` Miguel Ojeda
2024-11-08 13:20 ` Tamir Duberstein
2024-11-08 13:14 ` Miguel Ojeda
2024-11-08 13:13 ` Miguel Ojeda
2024-11-08 13:14 ` Tamir Duberstein
2024-11-04 21:20 ` [PATCH v2 3/6] rust: arc: split unsafe block, add missing comment Tamir Duberstein
2024-11-08 11:38 ` Alice Ryhl [this message]
2024-11-08 12:29 ` Tamir Duberstein
2024-11-08 12:37 ` Alice Ryhl
2024-11-08 12:40 ` Tamir Duberstein
2024-11-08 12:47 ` Alice Ryhl
2024-11-08 12:53 ` Tamir Duberstein
2024-11-04 21:20 ` [PATCH v2 4/6] rust: change `ForeignOwnable` pointer to mut Tamir Duberstein
2024-11-08 11:39 ` Alice Ryhl
2024-11-08 12:23 ` Tamir Duberstein
2024-11-04 21:20 ` [PATCH v2 5/6] rust: reorder `ForeignOwnable` items Tamir Duberstein
2024-11-08 11:42 ` Alice Ryhl
2024-11-04 21:20 ` [PATCH v2 6/6] rust: add improved version of `ForeignOwnable::borrow_mut` Tamir Duberstein
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=CAH5fLgiMHE5GXQv8pSR_KYWsa44zr1o_FNrg1mj8QuTvNQmXhQ@mail.gmail.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).