All of lore.kernel.org
 help / color / mirror / Atom feed
From: Allison Henderson <allison.henderson@oracle.com>
To: Catherine Hoang <catherine.hoang@oracle.com>, linux-xfs@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] xfsprogs: add error tags for log attribute replay test
Date: Wed, 10 Nov 2021 18:37:25 -0700	[thread overview]
Message-ID: <3c74fe87-ef85-a040-cf2c-f10f23902361@oracle.com> (raw)
In-Reply-To: <20211111001112.76438-1-catherine.hoang@oracle.com>

Hi Catherine,

These new tags look good to me.  If folks like new testcase I'll be 
happy to add these new tags to the larger log attr set.  You can add my 
rvb to these four error tag patches.

Reviewed-by: Allison Henderson <allison.henderson@oracle.com>

Thanks!
Allison


On 11/10/21 5:11 PM, 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_v25_extended
> 
> This set adds the new error tags leaf_split and leaf_to_node, which are used to
> inject errors in the tests.
> 
> 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  | 5 +++++
>   libxfs/xfs_errortag.h  | 6 +++++-
>   4 files changed, 17 insertions(+), 1 deletion(-)
> 

      parent reply	other threads:[~2021-11-11  1:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  0:11 [RFC PATCH 0/2] xfsprogs: add error tags for log attribute replay test Catherine Hoang
2021-11-11  0:11 ` [RFC PATCH 1/2] xfsprogs: add leaf split error tag Catherine Hoang
2021-11-11  0:11 ` [RFC PATCH 2/2] xfsprogs: add leaf to node " Catherine Hoang
2021-11-11  1:37 ` Allison Henderson [this message]

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=3c74fe87-ef85-a040-cf2c-f10f23902361@oracle.com \
    --to=allison.henderson@oracle.com \
    --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 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.