From: Aaron Thompson <dev@aaront.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Aaron Thompson <dev@aaront.org>
Subject: [PATCH 0/2] debugfs: Remove broken no-mount mode
Date: Thu, 20 Nov 2025 10:26:31 +0000 [thread overview]
Message-ID: <20251120102222.18371-1-dev@null.aaront.org> (raw)
Hi all,
This patch removes the debugfs no-mount mode because it hasn't worked as
intended for several years. When I noticed that it wasn't working, I first
started coding a fix, which is straightforward. But after looking into the
history, it seems pretty clear that this mode isn't being used, so I think it
makes more sense to remove it.
The code could be made a tiny bit simpler and more consistent if we change the
off mode error code from -EPERM to -ENOENT. That would make the off case and the
uninitialized case always the same. The documentation for the off mode
specifically says that the error code is -EPERM however, so I stuck with that
for now.
Thanks!
Aaron Thompson (2):
debugfs: Remove redundant access mode checks
debugfs: Remove broken no-mount mode
.../admin-guide/kernel-parameters.txt | 6 +---
fs/debugfs/inode.c | 36 ++++++-------------
fs/debugfs/internal.h | 13 -------
lib/Kconfig.debug | 9 +----
4 files changed, 13 insertions(+), 51 deletions(-)
base-commit: 6a23ae0a96a600d1d12557add110e0bb6e32730c
--
2.47.3
next reply other threads:[~2025-11-20 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:26 Aaron Thompson [this message]
2025-11-20 10:26 ` [PATCH 1/2] debugfs: Remove redundant access mode checks Aaron Thompson
2025-11-20 10:26 ` [PATCH 2/2] debugfs: Remove broken no-mount mode Aaron Thompson
2025-12-01 17:15 ` Mark Brown
2025-12-01 22:16 ` Aaron Thompson
2025-12-02 5:19 ` Greg Kroah-Hartman
2025-12-02 6:01 ` Chen-Yu Tsai
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=20251120102222.18371-1-dev@null.aaront.org \
--to=dev@aaront.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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).