All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: michaelc@cs.wisc.edu, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 4/4] libiscsi: return new error code when nop times out
Date: Wed, 30 Jul 2014 14:52:37 +0200	[thread overview]
Message-ID: <53D8EA95.4030104@suse.de> (raw)
In-Reply-To: <1405198311-64449-5-git-send-email-michaelc@cs.wisc.edu>

On 07/12/2014 10:51 PM, michaelc@cs.wisc.edu wrote:
> From: Mike Christie <michaelc@cs.wisc.edu>
>
> When a iscsi nop as ping timedout we were failing with the
> common connection error code, ISCSI_ERR_CONN_FAILED. This
> patch adds a new error code for this problem so can properly
> track/distinguish in userspace.
>
> Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
> ---
>   drivers/scsi/libiscsi.c |    2 +-
>   include/scsi/iscsi_if.h |    1 +
>   2 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/scsi/libiscsi.c b/drivers/scsi/libiscsi.c
> index f2db82b..b0813fd 100644
> --- a/drivers/scsi/libiscsi.c
> +++ b/drivers/scsi/libiscsi.c
> @@ -2097,7 +2097,7 @@ static void iscsi_check_transport_timeouts(unsigned long data)
>   				  conn->ping_timeout, conn->recv_timeout,
>   				  last_recv, conn->last_ping, jiffies);
>   		spin_unlock(&session->frwd_lock);
> -		iscsi_conn_failure(conn, ISCSI_ERR_CONN_FAILED);
> +		iscsi_conn_failure(conn, ISCSI_ERR_NOP_TIMEDOUT);
>   		return;
>   	}
>
> diff --git a/include/scsi/iscsi_if.h b/include/scsi/iscsi_if.h
> index fd0421c..95ed942 100644
> --- a/include/scsi/iscsi_if.h
> +++ b/include/scsi/iscsi_if.h
> @@ -527,6 +527,7 @@ enum iscsi_err {
>   	ISCSI_ERR_XMIT_FAILED		= ISCSI_ERR_BASE + 19,
>   	ISCSI_ERR_TCP_CONN_CLOSE	= ISCSI_ERR_BASE + 20,
>   	ISCSI_ERR_SCSI_EH_SESSION_RST	= ISCSI_ERR_BASE + 21,
> +	ISCSI_ERR_NOP_TIMEDOUT		= ISCSI_ERR_BASE + 22,
>   };
>
>   /*
>
Reviewed-by: Hannes Reinecke <hare@suse.de>

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

  reply	other threads:[~2014-07-30 12:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 20:51 [PATCH 0/4] iscsi: iscsi changes for 3.17 michaelc
2014-07-12 20:51 ` [PATCH 1/4] iscsi class: fix get_host_stats error handling michaelc
2014-07-30 12:50   ` Hannes Reinecke
2014-07-31 22:32     ` Mike Christie
2014-08-01 13:31       ` Hannes Reinecke
2014-08-01 16:10         ` Mike Christie
2014-07-12 20:51 ` [PATCH 2/4] qla4xxx: fix get_host_stats error propagation michaelc
2014-07-30 12:51   ` Hannes Reinecke
2014-07-12 20:51 ` [PATCH 3/4] iscsi class: fix get_host_stats return code when not supported michaelc
2014-07-30 12:52   ` Hannes Reinecke
2014-07-12 20:51 ` [PATCH 4/4] libiscsi: return new error code when nop times out michaelc
2014-07-30 12:52   ` Hannes Reinecke [this message]
2014-07-13  9:50 ` [PATCH 0/4] iscsi: iscsi changes for 3.17 Christoph Hellwig
2014-07-30 12:51   ` Vikas Chaudhary
2014-07-30 11:43 ` Christoph Hellwig

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=53D8EA95.4030104@suse.de \
    --to=hare@suse.de \
    --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 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.