From: Mike Snitzer <snitzer@redhat.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: linux-scsi@vger.kernel.org, agk@redhat.com, jaxboe@fusionio.com,
Hannes Reinecke <hare@suse.de>,
michaelc@cs.wisc.edu, Mike Snitzer <snitzer@redhat.com>
Subject: [PATCH v3 0/3] differentiate between I/O errors
Date: Fri, 14 Jan 2011 10:58:53 -0500 [thread overview]
Message-ID: <1295020736-27699-1-git-send-email-snitzer@redhat.com> (raw)
Refreshed against 2.6.38 merge window commit (52cfd503ad717).
Added Hannes' Acked-by to patch 2 and 3. Removed RFC tag from all
patches now that we have consensus.
James, it would be outstanding if we could get this squeezed in to the
2.6.38 merge. But if not, at least getting it staged in your tree for
2.6.39 merge would be great.
The non-scsi changes _could_ go through block and DM trees
respectively but I figured it easiest to keep the patchset together in
one tree (biggest change being SCSI it seemed to make sense to push
the changes through your tree).
sense).
Please advise, thanks.
Mike
Hannes Reinecke (1):
scsi: Detailed I/O errors
Mike Snitzer (2):
dm mpath: propagate target errors immediately
block: improve detail in I/O error messages
block/blk-core.c | 20 +++++++++++++++++---
drivers/md/dm-mpath.c | 11 +----------
drivers/scsi/scsi_error.c | 24 +++++++++++++++++-------
drivers/scsi/scsi_lib.c | 24 ++++++++++++++++++++++--
include/scsi/scsi.h | 3 +++
5 files changed, 60 insertions(+), 22 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-01-14 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 15:58 Mike Snitzer [this message]
2011-01-14 15:58 ` [PATCH v3 1/3] scsi: Detailed I/O errors Mike Snitzer
2011-01-14 16:10 ` Jonathan McDowell
2011-01-14 17:16 ` Mike Snitzer
2011-01-17 15:52 ` Hannes Reinecke
2011-01-17 18:20 ` Mike Snitzer
2011-01-14 15:58 ` [PATCH v3 2/3] dm mpath: propagate target errors immediately Mike Snitzer
2011-01-14 15:58 ` [PATCH v3 3/3] block: improve detail in I/O error messages Mike Snitzer
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=1295020736-27699-1-git-send-email-snitzer@redhat.com \
--to=snitzer@redhat.com \
--cc=James.Bottomley@suse.de \
--cc=agk@redhat.com \
--cc=hare@suse.de \
--cc=jaxboe@fusionio.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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