From: Eric Kerin <eric@bootseg.com>
To: "Larry W. Finger" <Larry.Finger@lwfinger.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Kernel oops in 2.6.1 when loading aha152x_cs.ko
Date: Fri, 09 Jan 2004 20:37:18 -0500 [thread overview]
Message-ID: <1073698638.2026.3.camel@opiate> (raw)
In-Reply-To: <6.0.0.22.0.20040109124348.01b86068@pop-server.kc.rr.com>
On Fri, 2004-01-09 at 15:14, Larry W. Finger wrote:
> + INIT_LIST_HEAD(&sht->legacy_hosts);
Under the non-pcmcia version of that driver, the above code is handled
by the module_init function (which is included from scsi_module.c), but
since that routine isn't used for the PCMCIA version, that list never
get's initialized.
The below patch handles it in the aha152x driver itself for PCMCIA(which
is the part that is technically broken). Instead of handling it in
hosts.c file.
Give this a try, it should work the same, but I don't have the hardware
to test it on.
Eric
-- linux-2.6.1/drivers/scsi/aha152x.c 2003-12-31 11:04:14.000000000
-0500
+++ linux-2.6.1/drivers/scsi/aha152x.c.listfix 2004-01-09
16:21:03.977748000 -0500
@@ -965,6 +965,12 @@ struct Scsi_Host *aha152x_probe_one(stru
{
struct Scsi_Host *shpnt;
+#ifdef PCMCIA
+ if(!&aha152x_driver_template->legacy_hosts){
+ INIT_LIST_HEAD(&aha152x_driver_template->legacy_hosts);
+ }
+#endif
+
shpnt = scsi_register(&aha152x_driver_template, sizeof(struct
aha152x_hostdata));
if (!shpnt) {
printk(KERN_ERR "aha152x: scsi_register failed\n");
next prev parent reply other threads:[~2004-01-10 1:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 20:14 Kernel oops in 2.6.1 when loading aha152x_cs.ko Larry W. Finger
2004-01-10 1:37 ` Eric Kerin [this message]
2004-01-10 5:27 ` Larry W. Finger
2004-01-10 6:38 ` Eric Kerin
2004-01-10 15:03 ` James Bottomley
2004-01-10 17:09 ` Larry W. Finger
2004-01-10 17:35 ` Juergen E. Fischer
2004-01-10 19:11 ` Eric Kerin
2004-01-10 20:43 ` 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=1073698638.2026.3.camel@opiate \
--to=eric@bootseg.com \
--cc=Larry.Finger@lwfinger.net \
--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;
as well as URLs for NNTP newsgroup(s).