public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alex.Iannicelli@Emulex.Com
Cc: linux-scsi@vger.kernel.org, James.Smart@Emulex.Com
Subject: Re: [PATCH 1/1] [SCSI] Clear Devloss Callback Done flag in fc_remote_port_rolechg.
Date: Thu, 03 Nov 2011 11:15:36 +0400	[thread overview]
Message-ID: <1320304536.11439.1.camel@dabdike> (raw)
In-Reply-To: <fc185e15-b38b-407a-a98b-bb65c53c5f78@exht2.ad.emulex.com>

On Thu, 2011-10-27 at 07:53 -0700, Alex.Iannicelli@Emulex.Com wrote:
> This patch fixes a bug where devloss is not called on fc_host teardown. The 
> issues is seen if the LLDD uses rport_rolechg to add target role to rport.
> When an rport is discovered the LLDD uses fc_rport_add to add the rport and then 
> uses remote_port_rolechg to indicate that it is a target. If this rport goes away 
> and the LLDD calls fc_report_port_delete. The transport calls devloss after the 
> devloss timer fires and it sets the FC_RPORT_DEVLOSS_CALLBK_DONE flag. If the
> LLDD discovers this target again and uses remote_port_add to add it, but it was
> a target and there is no target role assigned yet then this function returns 
> without clearing the FC_RPORT_DEVLOSS_CALLBACK_DONE flag. When the LLDD calls
> again to change the role to a target the report_port_rolechg routine neglects to
> clear the flag as well. Once in this state, if the LLDD tears down the fc_host
> then devloss will not be called for this target because the DEVLOSS_CALLBK_DONE
> flag is still set.
>  
> This patch adds the FC_RPORT_DEVLOSS_CALLBK_DONE flag to the group of flags that
> it clears when flushing devloss timers.
>  
> Signed-off-by: Alex Iannicelli <alex.iannicelli@emulex.com>
> Signed-off-by: James Smart <james.smart@emulex.com>

This patch has the usual outlook tab->space corruption.  Could you
resend it either with a working email client or as an attachment?

Thanks,

James



  reply	other threads:[~2011-11-03  7:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 14:53 [PATCH 1/1] [SCSI] Clear Devloss Callback Done flag in fc_remote_port_rolechg Alex.Iannicelli
2011-11-03  7:15 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-03 15:10 James Smart
     [not found] <1320333041.4568.3.camel@ogier>
2012-01-12 21:44 ` James Smart

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=1320304536.11439.1.camel@dabdike \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Alex.Iannicelli@Emulex.Com \
    --cc=James.Smart@Emulex.Com \
    --cc=linux-scsi@vger.kernel.org \
    /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