[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1452210511.15259.38.camel@HansenPartnership.com>
Date: Thu, 07 Jan 2016 15:48:31 -0800
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: "K. Y. Srinivasan" <kys@...rosoft.com>, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
ohering@...e.com, jbottomley@...allels.com, hch@...radead.org,
linux-scsi@...r.kernel.org, apw@...onical.com, vkuznets@...hat.com,
jasowang@...hat.com, martin.petersen@...cle.com, hare@...e.de
Cc: stable@...r.kernel.org
Subject: Re: [PATCH 1/1] scsi: scsi_transport_fc: Fix a bug in the error
handling function
On Thu, 2016-01-07 at 16:40 -0800, K. Y. Srinivasan wrote:
> The macro startget_to_rport() can return NULL; handle that case
> properly.
OK, can we unwind why you think you could possibly need this? It would
mean that fc_timed_out was called for a non-FC device, which was
thought to be an impossibility when the fc transport class was
designed.
James
> Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> Cc: <stable@...r.kernel.org>
> ---
> drivers/scsi/scsi_transport_fc.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/scsi/scsi_transport_fc.c
> b/drivers/scsi/scsi_transport_fc.c
> index 24eaaf6..42a908f 100644
> --- a/drivers/scsi/scsi_transport_fc.c
> +++ b/drivers/scsi/scsi_transport_fc.c
> @@ -2081,7 +2081,7 @@ fc_timed_out(struct scsi_cmnd *scmd)
> {
> struct fc_rport *rport = starget_to_rport(scsi_target(scmd
> ->device));
>
> - if (rport->port_state == FC_PORTSTATE_BLOCKED)
> + if ((rport == NULL) || (rport->port_state ==
> FC_PORTSTATE_BLOCKED))
> return BLK_EH_RESET_TIMER;
>
> return BLK_EH_NOT_HANDLED;
Powered by blists - more mailing lists