From: Hannes Reinecke <hare@suse.de>
To: Rob Evers <revers@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi_io_completion: soften unhandled error and sense messages
Date: Fri, 07 Oct 2011 09:29:48 +0200 [thread overview]
Message-ID: <4E8EAA6C.90102@suse.de> (raw)
In-Reply-To: <1317938931-6532-1-git-send-email-revers@redhat.com>
On 10/07/2011 12:08 AM, Rob Evers wrote:
> We are receiving reports that users are seeing error messages during
> fabric faults, but the systems are not malfunctioning. I previously
> submitted a patch which simply removed the offending messages but
> James Bottomley rejected this as we were losing error information.
>
> This patch softens the messages such that they don't appear to
> be error indications from the user perspective.
>
> new messages suggested by Mike Christie
>
> Signed-off-by: Rob Evers<revers@redhat.com>
> ---
> drivers/scsi/scsi_lib.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
> index fc3f168..ef2a8a1 100644
> --- a/drivers/scsi/scsi_lib.c
> +++ b/drivers/scsi/scsi_lib.c
> @@ -920,12 +920,13 @@ void scsi_io_completion(struct scsi_cmnd *cmd, unsigned int good_bytes)
> action = ACTION_FAIL;
> break;
> default:
> - description = "Unhandled sense code";
> + description =
> + "Extended sense description not available";
> action = ACTION_FAIL;
> break;
> }
> } else {
> - description = "Unhandled error code";
> + description = "Extended error description not available";
> action = ACTION_FAIL;
> }
>
Actually, I would prefer having this message routed via the
scsi_logging mechanism. Then it wouldn't bother the unsuspecting
user and we still would retain the information if scsi_logging is
enabled.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-10-07 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 22:08 [PATCH] scsi_io_completion: soften unhandled error and sense messages Rob Evers
2011-10-07 7:29 ` Hannes Reinecke [this message]
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=4E8EAA6C.90102@suse.de \
--to=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=revers@redhat.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.