From: Hannes Reinecke <hare@suse.de>
To: Ren Mingxin <renmx@cn.fujitsu.com>
Cc: James Bottomley <jbottomley@parallels.com>,
linux-scsi@vger.kernel.org, Dave Chinner <david@fromorbit.com>,
Theodore T'so <tytso@mit.edu>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/3] scsi: Document enhanced error codes
Date: Thu, 06 Jun 2013 08:58:07 +0200 [thread overview]
Message-ID: <51B032FF.9000607@suse.de> (raw)
In-Reply-To: <51B022F8.4000200@cn.fujitsu.com>
On 06/06/2013 07:49 AM, Ren Mingxin wrote:
> Hi, Hannes:
>
> I have two questions about the comments:
>
> On 06/05/2013 03:10 PM, Hannes Reinecke wrote:
>> Document the various error codes returned on I/O failure.
>>
>> Signed-off-by: Hannes Reinecke<hare@suse.de>
>> ---
>> drivers/scsi/scsi_error.c | 7 +++++--
>> drivers/scsi/scsi_lib.c | 11 +++++++++++
>> 2 files changed, 16 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
>> index f43de1e..443b0e3 100644
>> --- a/drivers/scsi/scsi_error.c
>> +++ b/drivers/scsi/scsi_error.c
>> @@ -229,8 +229,11 @@ static inline void scsi_eh_prt_fail_stats(struct
>> Scsi_Host *shost,
>> * scsi_check_sense - Examine scsi cmd sense
>> * @scmd: Cmd to have sense checked.
>> *
>> - * Return value:
>> - * SUCCESS or FAILED or NEEDS_RETRY or TARGET_ERROR
>> + * Possible return values:
>> + * SUCCESS
>> + * FAILED
>> + * NEEDS_RETRY
>> + * TARGET_ERROR
>
> This is more likely to be a historical non-update issue -
> there is another possible return value 'ADD_TO_MLQUEUE' which may be
> returned by the handler check_sense() or the case of this
> scsi_check_sense() below, right?
>
> switch (sshdr.sense_key) {
> case HARDWARE_ERROR:
> if (scmd->device->retry_hwerror)
> return ADD_TO_MLQUEUE;
>
Blast. You are correct. Will be fixing it up.
>>
>> *
>> * Notes:
>> * When a deferred error is detected the current command has
>> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
>> index 86d5220..12bfa73 100644
>> --- a/drivers/scsi/scsi_lib.c
>> +++ b/drivers/scsi/scsi_lib.c
>> @@ -700,6 +700,17 @@ void scsi_release_buffers(struct scsi_cmnd *cmd)
>> }
>> EXPORT_SYMBOL(scsi_release_buffers);
>>
>> +/**
>> + * __scsi_error_from_host_byte - translate SCSI error code into errno
>> + * @cmd: SCSI command (unused)
>> + * @result: scsi error code
>> + *
>> + * Translate SCSI error code into standard UNIX errno.
>> + * Return values:
>> + * -ENOLINK temporary transport failure
>> + * -EREMOTEIO permanent target failure, do not retry
>> + * -EBADE permanent nexus failure, retry on other path
>
> Sorry, I'm afraid that I'm not clear why '-EIO' is not listed here...
>
> Perhaps some of them are not necessary to document for some reasons?
>
Hmm. What with EIO being the default I've seen no need to document this.
But yes, you are right, it should be documented.
Cheers,
Hannes
next prev parent reply other threads:[~2013-06-06 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 7:10 [PATCH 0/3] scsi: More detailed I/O errors Hannes Reinecke
2013-06-05 7:10 ` [PATCH 1/3] scsi: Document enhanced error codes Hannes Reinecke
2013-06-06 5:49 ` Ren Mingxin
2013-06-06 6:58 ` Hannes Reinecke [this message]
2013-06-05 7:11 ` [PATCH 2/3] scsi: Return ENOSPC on thin provisioning failure Hannes Reinecke
2013-06-05 7:11 ` [PATCH 3/3] scsi: Return ENODATA on medium error Hannes Reinecke
2013-06-06 7:52 ` Ren Mingxin
2013-06-06 14:40 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 8:26 [PATCHv2 0/3] scsi: More detailed I/O errors Hannes Reinecke
2013-06-06 8:26 ` [PATCH 1/3] scsi: Document enhanced error codes 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=51B032FF.9000607@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 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.