From: "Darrick J. Wong" <djwong@kernel.org>
To: Catherine Hoang <catherine.hoang@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [RFC PATCH v3 0/2] xfsprogs: add error tags for log attribute replay test
Date: Tue, 1 Feb 2022 12:06:32 -0800 [thread overview]
Message-ID: <20220201200632.GP8313@magnolia> (raw)
In-Reply-To: <20220201171755.22651-1-catherine.hoang@oracle.com>
On Tue, Feb 01, 2022 at 05:17:53PM +0000, Catherine Hoang wrote:
> Hi all,
>
> These are the corresponding userspace changes for the new log attribute
> replay test. These are built on top of Allison’s logged attribute patch
> sets, which can be viewed here:
> https://github.com/allisonhenderson/xfs_work/tree/delayed_attrs_xfsprogs_v26_extended
>
> This set adds the new error tags da_leaf_split and larp_leaf_to_node,
> which are used to inject errors in the tests.
>
> v2->v3:
> Rename larp_leaf_split to da_leaf_split
With the XFS_ERRTAG_LARP_LEAF_TO_NODE -> XFS_ERRTAG_ATTR_LEAF_TO_NODE
change made, you can add:
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
For the whole series.
--D
>
> Suggestions and feedback are appreciated!
>
> Catherine
>
>
> Catherine Hoang (2):
> xfsprogs: add leaf split error tag
> xfsprogs: add leaf to node error tag
>
> io/inject.c | 2 ++
> libxfs/xfs_attr_leaf.c | 5 +++++
> libxfs/xfs_da_btree.c | 3 +++
> libxfs/xfs_errortag.h | 6 +++++-
> 4 files changed, 15 insertions(+), 1 deletion(-)
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-02-01 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 17:17 [RFC PATCH v3 0/2] xfsprogs: add error tags for log attribute replay test Catherine Hoang
2022-02-01 17:17 ` [RFC PATCH v3 1/2] xfsprogs: add leaf split error tag Catherine Hoang
2022-02-01 17:17 ` [RFC PATCH v3 2/2] xfsprogs: add leaf to node " Catherine Hoang
2022-02-01 20:06 ` Darrick J. Wong [this message]
2022-02-01 22:05 ` [RFC PATCH v3 0/2] xfsprogs: add error tags for log attribute replay test Catherine Hoang
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=20220201200632.GP8313@magnolia \
--to=djwong@kernel.org \
--cc=catherine.hoang@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox