From: Ziyang Zhang <ZiyangZhang@linux.alibaba.com>
To: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Cc: zlang@redhat.com, david@fromorbit.com, djwong@kernel.org,
hsiangkao@linux.alibaba.com, allison.henderson@oracle.com,
Ziyang Zhang <ZiyangZhang@linux.alibaba.com>
Subject: [PATCH V5 0/2] cleanup and bugfix for xfs tests related to btree format
Date: Thu, 8 Dec 2022 15:28:41 +0800 [thread overview]
Message-ID: <20221208072843.1866615-1-ZiyangZhang@linux.alibaba.com> (raw)
The first patch add a helper in common/xfs to export the inode core size
which is needed by some xfs test cases.
The second patch ensure that S_IFDIR.FMT_BTREE is in btree format while
populating dir.
V5:
- rename _xfs_inode_core_bytes() to _xfs_get_inode_core_bytes()
- rename _xfs_inode_size() to _xfs_get_inode_size()
- use one pipe in _xfs_get_inode_size()
- use local variables in __populate_xfs_create_btree_dir()
V4:
- let the new helper function accept the "missing" parameter
- make _xfs_inode_core_bytes echo 176 or 96 so tests can work correctly on
both v4 and v5
V3:
- refactor xfs tests cases using inode core size
V2:
- take Darrick's advice to cleanup code
Ziyang Zhang (2):
common/xfs: Add a helper to export inode core size
common/populate: Ensure that S_IFDIR.FMT_BTREE is in btree format
common/populate | 34 +++++++++++++++++++++++++++++++++-
common/xfs | 24 ++++++++++++++++++++++++
tests/xfs/335 | 3 ++-
tests/xfs/336 | 3 ++-
tests/xfs/337 | 3 ++-
tests/xfs/341 | 3 ++-
tests/xfs/342 | 3 ++-
7 files changed, 67 insertions(+), 6 deletions(-)
--
2.18.4
next reply other threads:[~2022-12-08 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 7:28 Ziyang Zhang [this message]
2022-12-08 7:28 ` [PATCH V5 1/2] common/xfs: Add a helper to export inode core size Ziyang Zhang
2022-12-08 7:28 ` [PATCH V5 2/2] common/populate: Ensure that S_IFDIR.FMT_BTREE is in btree format Ziyang Zhang
2022-12-09 16:37 ` Darrick J. Wong
2022-12-10 13:57 ` Zorro Lang
2022-12-11 2:30 ` Darrick J. Wong
2022-12-11 11:01 ` Zorro Lang
2022-12-11 11:23 ` Zorro Lang
2022-12-11 19:19 ` Darrick J. Wong
2022-12-12 3:43 ` Ziyang Zhang
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=20221208072843.1866615-1-ZiyangZhang@linux.alibaba.com \
--to=ziyangzhang@linux.alibaba.com \
--cc=allison.henderson@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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 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.