From: Benno Lossin <benno.lossin@proton.me>
To: "Antonio Hickey" <contact@byte-forge.io>,
"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>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: Antonio Hickey <contact@antoniohickey.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 16/16] rust: clippy: disable `addr_of[_mut]!` macros
Date: Sun, 16 Mar 2025 09:50:55 +0000 [thread overview]
Message-ID: <D8HLIR6LSOYB.1RC5ESP2Y0HWG@proton.me> (raw)
In-Reply-To: <20250316061429.817126-17-contact@antoniohickey.com>
On Sun Mar 16, 2025 at 7:14 AM CET, Antonio Hickey wrote:
> With the `raw_ref_op` feature enabled we no longer want to
> allow use of `addr_of!` and `addr_of_mut!` macros.
>
> We instead want to use `&raw` and `&raw mut` to get raw
`&raw const`
> pointers to a place.
>
> Note that this lint isn't currently reliable, but we enable
> it nevertheless because:
> 1. Document that one shouldn't use the `addr_of[_mut]!` macros.
> 2. When the lint becomes useful we will already have it enabled.
>
> Suggested-by: Benno Lossin <benno.lossin@proton.me>
> Link: https://github.com/Rust-for-Linux/linux/issues/1148
> Link: https://github.com/rust-lang/rust-clippy/issues/11431
> Signed-off-by: Antonio Hickey <contact@antoniohickey.com>
> ---
> .clippy.toml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/.clippy.toml b/.clippy.toml
> index 815c94732ed7..95c73959f039 100644
> --- a/.clippy.toml
> +++ b/.clippy.toml
> @@ -8,4 +8,8 @@ disallowed-macros = [
> # The `clippy::dbg_macro` lint only works with `std::dbg!`, thus we simulate
> # it here, see: https://github.com/rust-lang/rust-clippy/issues/11303.
> { path = "kernel::dbg", reason = "the `dbg!` macro is intended as a debugging tool" },
> + # With `raw_ref_op` feature enabled we no longer want to allow use of `addr_of!`
> + # and `addr_of_mut!` macros, but instead use `&raw` or `&raw mut`.
> + { path = "core::ptr::addr_of_mut", reason = "use `&raw mut` instead `addr_of_mut!`" },
> + { path = "core::ptr::addr_of", reason = "use `&raw` instead `addr_of!`" },
`&raw const`
---
Cheers,
Benno
> ]
next prev parent reply other threads:[~2025-03-16 9:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250316061429.817126-1-contact@antoniohickey.com>
2025-03-16 6:14 ` [PATCH v4 01/16] rust: enable `raw_ref_op` feature Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 02/16] rust: init: refactor to use `&raw [const|mut]` Antonio Hickey
2025-03-16 10:14 ` Benno Lossin
2025-03-16 6:14 ` [PATCH v4 03/16] rust: list: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 04/16] rust: task: " Antonio Hickey
2025-03-17 4:00 ` Boqun Feng
2025-03-16 6:14 ` [PATCH v4 05/16] rust: faux: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 06/16] rust: platform: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 07/16] rust: pci: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 08/16] rust: kunit: " Antonio Hickey
2025-03-18 8:02 ` David Gow
2025-03-20 1:39 ` Antonio Hickey
2025-03-20 23:15 ` Miguel Ojeda
2025-03-21 2:28 ` David Gow
2025-03-21 17:06 ` Boqun Feng
2025-03-21 19:04 ` Miguel Ojeda
2025-03-21 19:01 ` Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 09/16] rust: workqueue: " Antonio Hickey
2025-03-17 4:21 ` Boqun Feng
2025-03-17 4:32 ` Boqun Feng
2025-03-16 6:14 ` [PATCH v4 10/16] rust: rbtree: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 11/16] rust: net: phy: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 12/16] rust: sync: arc: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 13/16] rust: jump_label: " Antonio Hickey
2025-03-16 6:14 ` [PATCH v4 14/16] rust: fs: file: " Antonio Hickey
2025-03-17 4:33 ` Boqun Feng
2025-03-16 6:14 ` [PATCH v4 15/16] rust: block: " Antonio Hickey
2025-03-17 4:04 ` Boqun Feng
2025-03-16 6:14 ` [PATCH v4 16/16] rust: clippy: disable `addr_of[_mut]!` macros Antonio Hickey
2025-03-16 9:50 ` Benno Lossin [this message]
2025-03-16 12:57 ` 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=D8HLIR6LSOYB.1RC5ESP2Y0HWG@proton.me \
--to=benno.lossin@proton.me \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=contact@antoniohickey.com \
--cc=contact@byte-forge.io \
--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=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