All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catherine Hoang <catherine.hoang@oracle.com>
To: linux-xfs@vger.kernel.org
Subject: [RFC PATCH v2 0/2] xfsprogs: add error tags for log attribute replay test
Date: Mon, 10 Jan 2022 21:29:38 +0000	[thread overview]
Message-ID: <20220110212940.359823-1-catherine.hoang@oracle.com> (raw)

Hi all,

Just wanted to get this sent out again after the holidays. Original text
below:

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 larp_leaf_split and larp_leaf_to_node,
which are used to inject errors in the tests. 

v2 changes:
Updated naming scheme to make it clear that these error tags are meant to
trigger on the attribute code path for a replay

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  | 4 ++++
 libxfs/xfs_errortag.h  | 6 +++++-
 4 files changed, 16 insertions(+), 1 deletion(-)

-- 
2.25.1


             reply	other threads:[~2022-01-10 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 21:29 Catherine Hoang [this message]
2022-01-10 21:29 ` [RFC PATCH v2 1/2] xfsprogs: add leaf split error tag Catherine Hoang
2022-01-10 21:29 ` [RFC PATCH v2 2/2] xfsprogs: add leaf to node " Catherine Hoang
  -- strict thread matches above, loose matches on Subject: below --
2021-12-07  0:01 [RFC PATCH v2 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=20220110212940.359823-1-catherine.hoang@oracle.com \
    --to=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.