From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, guaneryu@gmail.com
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCHSET 0/2] fstests: test xfs_db directory navigation
Date: Mon, 22 Mar 2021 21:20:18 -0700 [thread overview]
Message-ID: <161647321880.3430916.13415014495565709258.stgit@magnolia> (raw)
Hi all,
Here are functional tests for a couple of xfs_db tests to improve the
usability of xfs_db by enabling users to navigate to inodes by path and
to list the contents of directories.
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
---
tests/xfs/917 | 98 ++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/917.out | 19 +++++++++
tests/xfs/918 | 109 +++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/918.out | 27 +++++++++++++
tests/xfs/group | 2 +
5 files changed, 255 insertions(+)
create mode 100755 tests/xfs/917
create mode 100644 tests/xfs/917.out
create mode 100755 tests/xfs/918
create mode 100644 tests/xfs/918.out
next reply other threads:[~2021-03-23 4:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 4:20 Darrick J. Wong [this message]
2021-03-23 4:20 ` [PATCH 1/2] xfs: test the xfs_db path command Darrick J. Wong
2021-03-25 9:33 ` Chandan Babu R
2021-03-25 16:33 ` Darrick J. Wong
2021-03-26 3:31 ` Chandan Babu R
2021-03-23 4:20 ` [PATCH 2/2] xfs: test the xfs_db ls command Darrick J. Wong
2021-03-25 10:08 ` Chandan Babu R
2021-03-25 16:35 ` Darrick J. Wong
2021-03-25 16:36 ` [PATCH v1.1 " Darrick J. Wong
2021-03-26 3:32 ` Chandan Babu R
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=161647321880.3430916.13415014495565709258.stgit@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.