mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxim Kozover <maximkoz@netvision.net.il>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	Michael Reed <mdr@sgi.com>,
	James.Smart@Emulex.Com
Subject: Re: Re: Re[8]: problems with scsi_transport_fc and qla2xxx
Date: Mon, 20 Mar 2006 13:45:59 +0300	[thread overview]
Message-ID: <1375487327.20060320134559@netvision.net.il> (raw)
In-Reply-To: <20060313231903.GK11755@andrew-vasquezs-powerbook-g4-15.local>

Hi Andrew!
Unfortunately I see that scan-work patch is not included in
2.6.16 and the usual lock appears:
#001:             [ffff8100708a8080] {scsi_host_alloc}
.. held by:         scsi_wq_4: 3912 [ffff810071edf870, 110]
... acquired at:               scsi_scan_target+0x51/0x87 [scsi_mod]

Applying the patch you sent solves the problem, i.e. disks appear again after
22 sec timeout (why?).

Thanks,

Maxim.

Tuesday, March 14, 2006, 2:19:03 AM, you wrote:

AV> diff --git a/drivers/scsi/scsi_transport_fc.c
AV> b/drivers/scsi/scsi_transport_fc.c
AV> index 929032e..3d09920 100644
AV> --- a/drivers/scsi/scsi_transport_fc.c
AV> +++ b/drivers/scsi/scsi_transport_fc.c
AV> @@ -1649,6 +1649,8 @@ fc_remote_port_delete(struct fc_rport  *
AV>                 return;
AV>         }
AV>  
AV> +       /* flush any scan work */ /* which can sleep */
AV> +       scsi_flush_work(rport_to_shost(rport));
AV>         scsi_target_block(&rport->dev);
AV>  
AV>         /* cap the length the devices can be blocked until they are deleted */



      reply	other threads:[~2006-03-20 11:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 12:05 Maxim Kozover
2006-02-27 18:05 ` Maxim Kozover
2006-03-01  6:14   ` Andrew Morton
2006-03-01 20:25     ` Stefan Kaltenbrunner
2006-03-01 21:08       ` Andrew Vasquez
2006-03-02 16:32         ` Maxim Kozover
2006-03-02 17:38           ` Andrew Vasquez
2006-03-02 22:15             ` Maxim Kozover
2006-03-06 19:06               ` Andrew Vasquez
2006-03-06 20:00           ` Mike Snitzer
2006-03-06 20:09             ` Maxim Kozover
2006-03-06 21:28               ` Andrew Vasquez
2006-03-06 20:57                 ` Maxim Kozover
2006-03-06 21:09                 ` Maxim Kozover
     [not found]                   ` <20060306232831.GS6278@andrew-vasquezs-powerbook-g4-15.local>
     [not found]                     ` <1219491790.20060307124035@netvision.net.il>
     [not found]                       ` <20060307172227.GE6275@andrew-vasquezs-powerbook-g4-15.local>
     [not found]                         ` <1343850424.20060307231141@netvision.net.il>
     [not found]                           ` <20060308080050.GF9956@andrew-vasquezs-powerbook-g4-15.local>
     [not found]                             ` <20060308154341.GA1779@andrew-vasquezs-powerbook-g4-15.local>
     [not found]                               ` <1502511597.20060308213247@netvision.net.il>
     [not found]                                 ` <20060310231344.GB641@andrew-vasquezs-powerbook-g4-15.local>
2006-03-11 21:10                                   ` Re[8]: " Maxim Kozover
2006-03-12  9:28                                     ` Arjan van de Ven
2006-03-12 11:46                                       ` Maxim Kozover
2006-03-13 23:19                                     ` Andrew Vasquez
2006-03-20 10:45                                       ` Maxim Kozover [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=1375487327.20060320134559@netvision.net.il \
    --to=maximkoz@netvision.net.il \
    --cc=James.Smart@Emulex.Com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mdr@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome