From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Jürgen E. Fischer" <fischer@linux-buechse.de>
Cc: Andrew Morton <akpm@osdl.org>,
bugme-daemon@bugzilla.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 6092] New: drivers/scsi/pcmcia/aha152x_stub.c: aha152x_resume(): variable used before set
Date: Sun, 19 Feb 2006 08:27:17 -0600 [thread overview]
Message-ID: <1140359237.3103.9.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20060218233151.GA1985@linux-buechse.de>
On Sun, 2006-02-19 at 00:31 +0100, Jürgen E. Fischer wrote:
> - just run the bh if the interrupt is from the controller and if so
> ensure that it's only called once per interrupt.
This is the bit that looks like the actual fix. It basically uses
service as a flag to debounce the interrupt.
This:
> HOSTDATA(shpnt)->in_intr++;
>
> + if( HOSTDATA(shpnt)->service==0 ) {
> + DO_UNLOCK(flags);
> + return;
> + }
Looks a bit wrong. If that ever triggered, you'd exit your task handler
with in_intr raised, which would cause a panic the next time
is_complete() was called.
The driver still seems to have an awful lot of locking confusion between
the host lock and its own internal lock (stored in the host structure).
I think there are several races and other nasties that could be cleaned
up simply by moving to using the host lock everywhere.
James
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-02-19 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602180209.k1I29meW030162@fire-2.osdl.org>
2006-02-18 5:10 ` [Bugme-new] [Bug 6092] New: drivers/scsi/pcmcia/aha152x_stub.c: aha152x_resume(): variable used before set Andrew Morton
2006-02-18 22:10 ` Jürgen E. Fischer
2006-02-18 22:14 ` Andrew Morton
2006-02-18 23:31 ` Jürgen E. Fischer
2006-02-18 23:46 ` Andrew Morton
2006-02-18 23:58 ` Jürgen E. Fischer
2006-02-19 14:27 ` James Bottomley [this message]
2006-02-19 15:08 ` Jürgen E. Fischer
2006-02-19 15:26 ` 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=1140359237.3103.9.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=fischer@linux-buechse.de \
--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