From: Carlos Maiolino <cmaiolino@redhat.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH 0/7] Configurable error behavior [V4]
Date: Wed, 11 May 2016 16:40:19 +0200 [thread overview]
Message-ID: <20160511144019.GB7828@redhat.com> (raw)
In-Reply-To: <20160511141558.GE42410@bfoster.bfoster>
On Wed, May 11, 2016 at 10:15:59AM -0400, Brian Foster wrote:
> On Tue, May 10, 2016 at 02:16:14PM +0200, Carlos Maiolino wrote:
> > New revision ot the patchset according with comments for V3.
> >
> > This patchset is aimed to implement a configurable error behavior in XFS, and,
> > most of the design has been done by Dave, so, I kept his signed-off.
> >
> > Detailed changelog is written on each patch, but, major changes are:
> >
> > - make fail_at_unmount a global configuration option inside
> > ../xfs/<dev>/err/fail_at_unmount
> >
>
> Any reason you didn't carry the reviewed-by tags from v3?
No reason Brian, I just completely forgot to carry the tags to the new version,
sorry for the extra work.
>
> For Dave's convenience (and based on the reviews of v3 and v4), for the
> series:
>
> Reviewed-by: Brian Foster <bfoster@redhat.com>
>
> > Carlos Maiolino (7):
> > xfs: configurable error behavior via sysfs
> > xfs: introduce metadata IO error class
> > xfs: add configurable error support to metadata buffers
> > xfs: introduce table-based init for error behaviors
> > xfs: add configuration of error failure speed
> > xfs: add configuration handlers for specific errors
> > xfs: add "fail at unmount" error handling configuration
> >
> > fs/xfs/xfs_buf.h | 20 ++++
> > fs/xfs/xfs_buf_item.c | 121 +++++++++++++--------
> > fs/xfs/xfs_mount.c | 22 +++-
> > fs/xfs/xfs_mount.h | 34 ++++++
> > fs/xfs/xfs_sysfs.c | 291 +++++++++++++++++++++++++++++++++++++++++++++++++-
> > fs/xfs/xfs_sysfs.h | 3 +
> > fs/xfs/xfs_trace.h | 1 -
> > 7 files changed, 446 insertions(+), 46 deletions(-)
> >
> > --
> > 2.4.11
> >
> > _______________________________________________
> > xfs mailing list
> > xfs@oss.sgi.com
> > http://oss.sgi.com/mailman/listinfo/xfs
--
Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-05-11 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 12:16 [PATCH 0/7] Configurable error behavior [V4] Carlos Maiolino
2016-05-10 12:16 ` [PATCH 1/7] xfs: configurable error behavior via sysfs Carlos Maiolino
2016-05-10 12:16 ` [PATCH 2/7] xfs: introduce metadata IO error class Carlos Maiolino
2016-05-10 12:16 ` [PATCH 3/7] xfs: add configurable error support to metadata buffers Carlos Maiolino
2016-05-11 14:15 ` Brian Foster
2016-05-10 12:16 ` [PATCH 4/7] xfs: introduce table-based init for error behaviors Carlos Maiolino
2016-05-10 12:16 ` [PATCH 5/7] xfs: add configuration of error failure speed Carlos Maiolino
2016-05-10 12:16 ` [PATCH 6/7] xfs: add configuration handlers for specific errors Carlos Maiolino
2016-05-11 14:15 ` Brian Foster
2016-05-10 12:16 ` [PATCH 7/7] xfs: add "fail at unmount" error handling configuration Carlos Maiolino
2016-05-11 14:15 ` Brian Foster
2016-05-11 14:39 ` Carlos Maiolino
2016-05-11 14:15 ` [PATCH 0/7] Configurable error behavior [V4] Brian Foster
2016-05-11 14:40 ` Carlos Maiolino [this message]
2016-05-11 23:23 ` Dave Chinner
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=20160511144019.GB7828@redhat.com \
--to=cmaiolino@redhat.com \
--cc=xfs@oss.sgi.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.