From: "Darrick J. Wong" <djwong@kernel.org>
To: sandeen@sandeen.net, djwong@kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: [PATCHSET v3 0/2] xfs_db: add minimal directory navigation
Date: Fri, 15 Jan 2021 17:24:25 -0800 [thread overview]
Message-ID: <161076026570.3386403.8299786881687962135.stgit@magnolia> (raw)
Hi all,
This patchset improves the usability of xfs_db by enabling users to
navigate to inodes by path and to list the contents of directories.
v2: Various cleanups and reorganizing suggested by dchinner
v3: Rebase to 5.10-rc0
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
xfsprogs git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=xfs_db-directory-navigation
fstests git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=xfs_db-directory-navigation
---
db/Makefile | 3
db/command.c | 1
db/command.h | 1
db/namei.c | 612 ++++++++++++++++++++++++++++++++++++++++++++++
libxfs/libxfs_api_defs.h | 1
man/man8/xfs_db.8 | 20 ++
6 files changed, 637 insertions(+), 1 deletion(-)
create mode 100644 db/namei.c
next reply other threads:[~2021-01-16 1:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 1:24 Darrick J. Wong [this message]
2021-01-16 1:24 ` [PATCH 1/2] xfs_db: add a directory path lookup command Darrick J. Wong
2021-01-20 12:35 ` Chandan Babu R
2021-01-20 17:39 ` Darrick J. Wong
2021-01-16 1:24 ` [PATCH 2/2] xfs_db: add an ls command Darrick J. Wong
2021-01-20 15:24 ` Chandan Babu R
-- strict thread matches above, loose matches on Subject: below --
2021-01-09 6:27 [PATCHSET v3 0/2] xfs_db: add minimal directory navigation Darrick J. Wong
2020-12-31 22:38 2020 NYE Patchbomb Guide! Darrick J. Wong
2020-12-31 22:46 ` [PATCHSET v3 0/2] xfs_db: add minimal directory navigation Darrick J. Wong
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=161076026570.3386403.8299786881687962135.stgit@magnolia \
--to=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).