From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: [PATCH] xfs_io: print sysfs paths of mounted filesystems
Date: Sun, 2 Jun 2024 16:29:49 -0700 [thread overview]
Message-ID: <20240602232949.GZ52987@frogsfrogsfrogs> (raw)
From: Darrick J. Wong <djwong@kernel.org>
Enable users to print the sysfs or debugfs path for the filesystems
backing the open files.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
io/fsuuid.c | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++++
man/man8/xfs_io.8 | 7 +++++
2 files changed, 75 insertions(+)
diff --git a/io/fsuuid.c b/io/fsuuid.c
index af2f87a20209..8e50ec14c8fd 100644
--- a/io/fsuuid.c
+++ b/io/fsuuid.c
@@ -12,6 +12,7 @@
#include "libfrog/logging.h"
static cmdinfo_t fsuuid_cmd;
+static cmdinfo_t sysfspath_cmd;
static int
fsuuid_f(
@@ -35,6 +36,62 @@ fsuuid_f(
return 0;
}
+#ifndef FS_IOC_GETFSSYSFSPATH
+struct fs_sysfs_path {
+ __u8 len;
+ __u8 name[128];
+};
+#define FS_IOC_GETFSSYSFSPATH _IOR(0x15, 1, struct fs_sysfs_path)
+#endif
+
+static void
+sysfspath_help(void)
+{
+ printf(_(
+"\n"
+" print the sysfs path for the open file\n"
+"\n"
+" Prints the path in sysfs where one might find information about the\n"
+" filesystem backing the open files. The path is not required to exist.\n"
+" -d -- return the path in debugfs, if any\n"
+"\n"));
+}
+
+static int
+sysfspath_f(
+ int argc,
+ char **argv)
+{
+ struct fs_sysfs_path path;
+ bool debugfs = false;
+ int c;
+ int ret;
+
+ while ((c = getopt(argc, argv, "d")) != EOF) {
+ switch (c) {
+ case 'd':
+ debugfs = true;
+ break;
+ default:
+ exitcode = 1;
+ return command_usage(&sysfspath_cmd);
+ }
+ }
+
+ ret = ioctl(file->fd, FS_IOC_GETFSSYSFSPATH, &path);
+ if (ret) {
+ xfrog_perror(ret, "FS_IOC_GETSYSFSPATH");
+ exitcode = 1;
+ return 0;
+ }
+
+ if (debugfs)
+ printf("/sys/kernel/debug/%.*s\n", path.len, path.name);
+ else
+ printf("/sys/fs/%.*s\n", path.len, path.name);
+ return 0;
+}
+
void
fsuuid_init(void)
{
@@ -46,4 +103,15 @@ fsuuid_init(void)
fsuuid_cmd.oneline = _("get mounted filesystem UUID");
add_command(&fsuuid_cmd);
+
+ sysfspath_cmd.name = "sysfspath";
+ sysfspath_cmd.cfunc = sysfspath_f;
+ sysfspath_cmd.argmin = 0;
+ sysfspath_cmd.argmax = -1;
+ sysfspath_cmd.args = _("-d");
+ sysfspath_cmd.flags = CMD_NOMAP_OK | CMD_FLAG_FOREIGN_OK;
+ sysfspath_cmd.oneline = _("get mounted filesystem sysfs path");
+ sysfspath_cmd.help = sysfspath_help;
+
+ add_command(&sysfspath_cmd);
}
diff --git a/man/man8/xfs_io.8 b/man/man8/xfs_io.8
index 56abe000f235..3ce280a75b4a 100644
--- a/man/man8/xfs_io.8
+++ b/man/man8/xfs_io.8
@@ -1464,6 +1464,13 @@ flag.
.TP
.B fsuuid
Print the mounted filesystem UUID.
+.TP
+.B sysfspath
+Print the sysfs or debugfs path for the mounted filesystem.
+
+The
+.B -d
+option selects debugfs instead of sysfs.
.SH OTHER COMMANDS
next reply other threads:[~2024-06-02 23:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1om_d115LQlficlrvs8z5v0InzJMyVDs_WfIJ1ttxO6uOL4FNNGJWtpebpaOoO0MIL7ZUgh7Xm224Eb-aKVaAg==@protonmail.internalid>
2024-06-02 23:29 ` Darrick J. Wong [this message]
2024-06-03 12:49 ` [PATCH] xfs_io: print sysfs paths of mounted filesystems Carlos Maiolino
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=20240602232949.GZ52987@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-xfs@vger.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