From: Matthew Maurer <mmaurer@google.com>
To: "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>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Timur Tabi" <ttabi@nvidia.com>,
"Benno Lossin" <lossin@kernel.org>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
Matthew Maurer <mmaurer@google.com>
Subject: [PATCH v6 3/5] rust: debugfs: Support arbitrary owned backing for File
Date: Wed, 18 Jun 2025 02:28:15 +0000 [thread overview]
Message-ID: <20250618-debugfs-rust-v6-3-72cae211b133@google.com> (raw)
In-Reply-To: <20250618-debugfs-rust-v6-0-72cae211b133@google.com>
This allows `File`s to be backed by `Deref<Target=T>` rather than just
`&'static T`. This means that dynamically allocated objects can be
attached to `File`s without needing to take extra steps to create a
pinned reference that's guaranteed to live long enough.
Signed-off-by: Matthew Maurer <mmaurer@google.com>
---
rust/kernel/debugfs.rs | 51 ++++++++++++++++++++++++++++++++++++++------------
1 file changed, 39 insertions(+), 12 deletions(-)
diff --git a/rust/kernel/debugfs.rs b/rust/kernel/debugfs.rs
index 6a89557d8cf49327d2984d15741ffb6640defd70..cd83f21cf2818f406575941ebbc6c426575643e4 100644
--- a/rust/kernel/debugfs.rs
+++ b/rust/kernel/debugfs.rs
@@ -5,12 +5,13 @@
//!
//! C header: [`include/linux/debugfs.h`](srctree/include/linux/debugfs.h)
-#[cfg(CONFIG_DEBUG_FS)]
+use crate::alloc::KBox;
use crate::prelude::GFP_KERNEL;
use crate::str::CStr;
#[cfg(CONFIG_DEBUG_FS)]
use crate::sync::Arc;
use core::fmt::Display;
+use core::ops::Deref;
#[cfg(CONFIG_DEBUG_FS)]
mod display_file;
@@ -61,40 +62,59 @@ fn create(_name: &CStr, _parent: Option<&Dir>) -> Self {
}
#[cfg(CONFIG_DEBUG_FS)]
- fn create_file<T: Display + Sized>(&self, name: &CStr, data: &'static T) -> File {
+ fn create_file<D: Deref<Target = T> + 'static + Send + Sync, T: Display>(
+ &self,
+ name: &CStr,
+ data: D,
+ ) -> File {
+ let mut file = File {
+ _entry: entry::Entry::empty(),
+ _data: None,
+ };
+ let Some(data) = KBox::new(data, GFP_KERNEL).ok() else {
+ return file;
+ };
+
let Some(parent) = &self.0 else {
- return File {
- _entry: entry::Entry::empty(),
- };
+ return file;
};
+
// SAFETY:
// * `name` is a NUL-terminated C string, living across the call, by `CStr` invariant.
// * `parent` is a live `dentry` since we have a reference to it.
// * `vtable` is all stock `seq_file` implementations except for `open`.
// `open`'s only requirement beyond what is provided to all open functions is that the
// inode's data pointer must point to a `T` that will outlive it, which we know because
- // we have a static reference.
+ // we have an owning `D` in the `File`, and we tear down the file during `Drop`.
let ptr = unsafe {
bindings::debugfs_create_file_full(
name.as_char_ptr(),
0o444,
parent.as_ptr(),
- data as *const _ as *mut _,
+ data.deref() as *const _ as *mut _,
core::ptr::null(),
&<T as display_file::DisplayFile>::VTABLE,
)
};
+ file._data = Some(data);
+
// SAFETY: `debugfs_create_file_full` either returns an error code or a legal
// dentry pointer, so `Entry::new` is safe to call here.
- let entry = unsafe { entry::Entry::new(ptr, Some(parent.clone())) };
+ file._entry = unsafe { entry::Entry::new(ptr, Some(parent.clone())) };
- File { _entry: entry }
+ file
}
#[cfg(not(CONFIG_DEBUG_FS))]
- fn create_file<T: Display + Sized>(&self, _name: &CStr, _data: &'static T) -> File {
- File {}
+ fn create_file<D: Deref<Target = T> + 'static + Send + Sync, T: Display>(
+ &self,
+ _name: &CStr,
+ data: D,
+ ) -> File {
+ File {
+ _data: KBox::new(data, GFP_KERNEL).ok().map(|x| x as _),
+ }
}
/// Create a DebugFS subdirectory.
@@ -125,7 +145,11 @@ pub fn subdir(&self, name: &CStr) -> Self {
/// dir.display_file(c_str!("foo"), &200);
/// // "my_debugfs_dir/foo" now contains the number 200.
/// ```
- pub fn display_file<T: Display + Sized>(&self, name: &CStr, data: &'static T) -> File {
+ pub fn display_file<D: Deref<Target = T> + 'static + Send + Sync, T: Display>(
+ &self,
+ name: &CStr,
+ data: D,
+ ) -> File {
self.create_file(name, data)
}
@@ -147,4 +171,7 @@ pub fn new(name: &CStr) -> Self {
pub struct File {
#[cfg(CONFIG_DEBUG_FS)]
_entry: entry::Entry,
+ // The data needs to be kept in a `Box` to prevent it from moving when the file does, as
+ // this might invalidate the pointer that's been passed to debugfs.
+ _data: Option<KBox<dyn Send + Sync>>,
}
--
2.50.0.rc2.696.g1fc2a0284f-goog
next prev parent reply other threads:[~2025-06-18 2:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 2:28 [PATCH v6 0/5] rust: DebugFS Bindings Matthew Maurer
2025-06-18 2:28 ` [PATCH v6 1/5] rust: debugfs: Bind DebugFS directory creation Matthew Maurer
2025-06-18 10:04 ` Danilo Krummrich
2025-06-18 2:28 ` [PATCH v6 2/5] rust: debugfs: Bind file creation for long-lived Display Matthew Maurer
2025-06-18 15:39 ` Danilo Krummrich
2025-06-18 15:56 ` Alice Ryhl
2025-06-18 2:28 ` Matthew Maurer [this message]
2025-06-18 8:19 ` [PATCH v6 3/5] rust: debugfs: Support arbitrary owned backing for File Alice Ryhl
2025-06-18 15:00 ` Matthew Maurer
2025-06-18 15:32 ` Danilo Krummrich
2025-06-18 2:28 ` [PATCH v6 4/5] rust: debugfs: Support format hooks Matthew Maurer
2025-06-18 2:28 ` [PATCH v6 5/5] rust: samples: Add debugfs sample Matthew Maurer
2025-06-18 15:52 ` Danilo Krummrich
2025-06-18 8:21 ` [PATCH v6 0/5] rust: DebugFS Bindings Alice Ryhl
2025-06-24 11:37 ` Dirk Behme
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=20250618-debugfs-rust-v6-3-72cae211b133@google.com \
--to=mmaurer@google.com \
--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=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=tmgross@umich.edu \
--cc=ttabi@nvidia.com \
/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).