From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "James E.J. Bottomley" <James.Bottomley@suse.de>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] qla1280: Drop host_lock while requesting firmware
Date: Sat, 23 Jan 2010 20:17:52 +0100 [thread overview]
Message-ID: <201001232018.08155.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <1264272029.373.95.camel@localhost>
[-- Attachment #1: Type: Text/Plain, Size: 1218 bytes --]
Ben Hutchings wrote:
> request_firmware() may sleep and it appears to be safe to release the
> spinlock here.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> Cc: stable@kernel.org
> ---
> This change was made in Debian kernel packages to address this bug
> report: <http://bugs.debian.org/543244>. We have applied it to 2.6.31
> and 2.6.32 and there have been no further bug reports on this driver.
>
> Ben.
>
> drivers/scsi/qla1280.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/scsi/qla1280.c b/drivers/scsi/qla1280.c
> index 8371d91..49ac414 100644
> --- a/drivers/scsi/qla1280.c
> +++ b/drivers/scsi/qla1280.c
> @@ -1640,8 +1640,10 @@ qla1280_load_firmware_pio(struct scsi_qla_host *ha)
I think that those request_firmware stuff together with it's error handling
should be moved from qla1280_load_firmware_pio() and
qla1280_load_firmware_dma() to qla1280_load_firmware().
Although the firmware version in the driver struct is updated before it is
updated, which may still fail. In that case it is not set back to the old
value. I don't know if that is a problem at all, that's just what I saw on a
quick look.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-01-23 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 18:40 [PATCH] qla1280: Drop host_lock while requesting firmware Ben Hutchings
2010-01-23 19:17 ` Rolf Eike Beer [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=201001232018.08155.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=James.Bottomley@suse.de \
--cc=ben@decadent.org.uk \
--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 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.