From: Mark Tinguely <tinguely@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: don't verify buffers after IO errors
Date: Thu, 28 Feb 2013 09:37:50 -0600 [thread overview]
Message-ID: <512F79CE.4030502@sgi.com> (raw)
In-Reply-To: <1361931954-11105-1-git-send-email-david@fromorbit.com>
On 02/26/13 20:25, Dave Chinner wrote:
> From: Dave Chinner<dchinner@redhat.com>
>
> When we read a buffer, we might get an error from the underlying
> block device and not the real data. Hence if we get an IO error, we
> shouldn't run the verifier but instead just pass the IO error
> straight through.
>
> Signed-off-by: Dave Chinner<dchinner@redhat.com>
> ---
Looks good. needs to go into Linux 3.7/8 stable?
Reviewed-by: Mark Tinguely <tinguely@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-28 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 2:25 [PATCH] xfs: don't verify buffers after IO errors Dave Chinner
2013-02-28 15:37 ` Mark Tinguely [this message]
2013-02-28 17:24 ` Ben Myers
2013-02-28 19:34 ` Dave Chinner
2013-03-07 18:46 ` Ben Myers
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=512F79CE.4030502@sgi.com \
--to=tinguely@sgi.com \
--cc=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox