From: "Gary Guo" <gary@garyguo.net>
To: git@younes.io, "Andreas Hindborg" <a.hindborg@kernel.org>,
"Breno Leitao" <leitao@debian.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rust: configfs: skip unregister after failed registration
Date: Tue, 18 Aug 2026 11:49:04 +0100 [thread overview]
Message-ID: <DKS0EN4DLKW3.IB8Z5VB3B7YG@garyguo.net> (raw)
In-Reply-To: <20260818-fix-rust-configfs-registration-state-v1-v1-1-c929990bc8ef@younes.io>
On Tue Aug 18, 2026 at 9:11 AM BST, Younes Akhouayri via B4 Relay wrote:
> From: Younes Akhouayri <git@younes.io>
>
> Subsystem::new() calls configfs_register_subsystem() from a fallible
> pin_chain callback. If registration fails, ChainPinInit drops the
> already initialized Subsystem. Its PinnedDrop currently calls
> configfs_unregister_subsystem() unconditionally.
>
> configfs_unregister_subsystem() requires registration to have completed
> and immediately dereferences the subsystem dentry. Registering a
> duplicate subsystem name returns -EEXIST before installing that dentry,
> so the cleanup path dereferences NULL and panics the kernel.
>
> Track successful registration explicitly and only unregister in that
> state. Keep mutex destruction unconditional because it is initialized
> before registration.
>
> Fixes: 446cafc295bf ("rust: configfs: introduce rust support for configfs")
> Signed-off-by: Younes Akhouayri <git@younes.io>
> ---
> rust/kernel/configfs.rs | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/rust/kernel/configfs.rs b/rust/kernel/configfs.rs
> index cd082b83e9e7..f358e227ce09 100644
> --- a/rust/kernel/configfs.rs
> +++ b/rust/kernel/configfs.rs
> @@ -130,6 +130,7 @@ pub struct Subsystem<Data> {
> subsystem: Opaque<bindings::configfs_subsystem>,
> #[pin]
> data: Data,
> + registered: bool,
No flag just for destruction. Please change new logic to avoid needing this.
Best,
Gary
> }
>
> // SAFETY: We do not provide any operations on `Subsystem`.
> @@ -173,12 +174,15 @@ pub fn new(
> }
> ),
> data <- data,
> + registered: false,
> })
> - .pin_chain(|this| {
> + .pin_chain(|mut this| {
> crate::error::to_result(
> // SAFETY: We initialized `this.subsystem` according to C API contract above.
> unsafe { bindings::configfs_register_subsystem(this.subsystem.get()) },
> - )
> + )?;
> + *this.as_mut().project().registered = true;
> + Ok(())
> })
> }
> }
> @@ -186,8 +190,10 @@ pub fn new(
> #[pinned_drop]
> impl<Data> PinnedDrop for Subsystem<Data> {
> fn drop(self: Pin<&mut Self>) {
> - // SAFETY: We registered `self.subsystem` in the initializer returned by `Self::new`.
> - unsafe { bindings::configfs_unregister_subsystem(self.subsystem.get()) };
> + if self.registered {
> + // SAFETY: `registered` is only set after `self.subsystem` was registered.
> + unsafe { bindings::configfs_unregister_subsystem(self.subsystem.get()) };
> + }
> // SAFETY: We initialized the mutex in `Subsystem::new`.
> unsafe { bindings::mutex_destroy(&raw mut (*self.subsystem.get()).su_mutex) };
> }
>
> ---
> base-commit: 47f27155f17498fccb1f222f79089642337498a9
> change-id: 20260817-fix-rust-configfs-registration-state-v1-fa33fcc69673
>
> Best regards,
> --
> Younes Akhouayri <git@younes.io>
next prev parent reply other threads:[~2026-08-18 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8L_eiohtkr-KVK8wOx5hbz_bo8XmfV8FHHX0zNjlG9RROwHwX_qm_KwmORgQkKq0k06TyMCArt_3HoW5QoGM4A==@protonmail.internalid>
2026-08-18 8:11 ` [PATCH] rust: configfs: skip unregister after failed registration Younes Akhouayri via B4 Relay
2026-08-18 9:37 ` Andreas Hindborg
2026-08-18 10:09 ` Andreas Hindborg
2026-08-18 10:49 ` Gary Guo [this message]
2026-08-18 10:53 ` Andreas Hindborg
2026-08-18 11:00 ` Gary Guo
2026-08-18 12:24 ` Andreas Hindborg
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=DKS0EN4DLKW3.IB8Z5VB3B7YG@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=git@younes.io \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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