From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <jbottomley@parallels.com>
Cc: linux-scsi@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
Theodore T'so <tytso@mit.edu>,
linux-fsdevel@vger.kernel.org, Ren Mingxin <renmx@cn.fujitsu.com>,
Hannes Reinecke <hare@suse.de>
Subject: [PATCHv2 0/3] scsi: More detailed I/O errors
Date: Thu, 6 Jun 2013 10:26:04 +0200 [thread overview]
Message-ID: <1370507167-35998-1-git-send-email-hare@suse.de> (raw)
As discussed at LSF the SCSI stack already knows about several
error conditions, it's just not well documented.
Also there are some more conditions upper layers might be
interested in.
This patchset improves the documentation of the existing
I/O error codes and adds two more error codes, ENOSPC
for thin provisioning failure and ENODATA for medium error.
Changes since the initial version, suggested by Ren Mingxin:
- Add error description to blk_update_request()
- Document missing values
Hannes Reinecke (3):
scsi: Document enhanced error codes
scsi: Return ENOSPC on thin provisioning failure
scsi: Return ENODATA on medium error
block/blk-core.c | 6 ++++++
drivers/scsi/scsi_error.c | 27 +++++++++++++++++++++++----
drivers/scsi/scsi_lib.c | 22 ++++++++++++++++++++++
include/scsi/scsi.h | 4 ++++
4 files changed, 55 insertions(+), 4 deletions(-)
--
1.7.12.4
next reply other threads:[~2013-06-06 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 8:26 Hannes Reinecke [this message]
2013-06-06 8:26 ` [PATCH 1/3] scsi: Document enhanced error codes Hannes Reinecke
2013-06-06 8:26 ` [PATCH 2/3] scsi: Return ENOSPC on thin provisioning failure Hannes Reinecke
2013-06-06 8:26 ` [PATCH 3/3] scsi: Return ENODATA on medium error Hannes Reinecke
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=1370507167-35998-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=david@fromorbit.com \
--cc=jbottomley@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=renmx@cn.fujitsu.com \
--cc=tytso@mit.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;
as well as URLs for NNTP newsgroup(s).