public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: James Bottomley <James.Bottomley@SteelEye.com>,
	Jeff Garzik <jgarzik@pobox.com>
Cc: Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] qla2xxx: fix bad locking during eh_abort
Date: Fri, 27 May 2005 13:18:31 -0700	[thread overview]
Message-ID: <20050527201831.GE16474@plap.qlogic.org> (raw)
In-Reply-To: <1117224371.7379.21.camel@mulgrave>

On Fri, 27 May 2005, James Bottomley wrote:

> On Thu, 2005-05-26 at 16:19 -0700, Andrew Vasquez wrote:
> > Please apply, this should go in before 2.6.12 is released.
> 
> I've got it in the rc-fixes tree for scsi.  However:
> 
> > +	spin_unlock(&ha->hardware_lock);
> 
> Should be spin_unlock_irq(&ha->hardware_lock); shouldn't it?  Otherwise
> we could sleep with interrupts disabled and the kernel now squeaks about
> that.

Yes, with the latest changes being proposed/implemented by Jeff G.,
there would need to be some additional massaging of the driver's
eh_*() routines.

Are you planning on putting the host_lock-free changes in for -rc,
I figured that would be going into the next kernel rev.  I mention
that because I have a block of patches which I have queued-up to add
new chip support to the driver.

Jeff, could you drop the qla2xxx driver from your scrubing
host_lock-free changes.  I'll go ahead and post an updated patch
following the patches in my queue.

Thanks,
Andrew Vasquez

  reply	other threads:[~2005-05-27 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 23:19 [PATCH] qla2xxx: fix bad locking during eh_abort Andrew Vasquez
2005-05-27 20:06 ` James Bottomley
2005-05-27 20:18   ` Andrew Vasquez [this message]
2005-05-27 20:30     ` Jeff Garzik
2005-05-27 20:38       ` James Bottomley
2005-05-27 20:42         ` Jeff Garzik
2005-05-27 22:04           ` Andrew Vasquez
2005-05-27 22:47             ` Jeff Garzik
2005-05-27 20:31     ` James Bottomley

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=20050527201831.GE16474@plap.qlogic.org \
    --to=andrew.vasquez@qlogic.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=jgarzik@pobox.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