linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	"Tarte, Robert" <Robert_Tarte@adaptec.com>
Subject: Re: [RFC] aic94xx: attaching to the sas transport class
Date: Mon, 6 Mar 2006 00:26:14 -0800	[thread overview]
Message-ID: <20060306082614.GA27603@us.ibm.com> (raw)
In-Reply-To: <1141339085.3238.80.camel@mulgrave.il.steeleye.com>


Ran into a issue that on the first load I did not have the
attach_HostRAID=1 that I need for my model of card so when I went to do a
modprobe -r; modprobe I got an oops. The patch below helps with the
describe case, but does not fix the problem of not being able to unload if
devices are found.

-andmike
--
Michael Anderson
andmike@us.ibm.com

 drivers/scsi/sas/sas_init.c |    2 ++
 1 files changed, 2 insertions(+)

Index: sas-2.6-patched/drivers/scsi/sas/sas_init.c
===================================================================
--- sas-2.6-patched.orig/drivers/scsi/sas/sas_init.c	2006-03-03 00:07:04.000000000 -0800
+++ sas-2.6-patched/drivers/scsi/sas/sas_init.c	2006-03-05 23:26:21.000000000 -0800
@@ -145,6 +145,8 @@ static int __init sas_class_init(void)
 
 static void __exit sas_class_exit(void)
 {
+	if (sas_transport_template)
+		sas_release_transport(sas_transport_template);
 	if (sas_task_cache)
 		kmem_cache_destroy(sas_task_cache);
 }

  parent reply	other threads:[~2006-03-06  8:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 22:38 [RFC] aic94xx: attaching to the sas transport class James Bottomley
2006-03-02 23:13 ` Mike Anderson
2006-03-03  2:16   ` Mark Rustad
2006-03-03  4:04     ` Randy.Dunlap
2006-03-03 16:51       ` Mark Rustad
2006-03-03 15:51     ` Stefan Richter
2006-03-03 18:24       ` Luben Tuikov
2006-03-03  4:34   ` James Bottomley
2006-03-04  1:47     ` Alexis Bruemmer
2006-03-03 10:26   ` Luben Tuikov
2006-03-03 16:12     ` Stefan Richter
2006-03-03 18:26       ` Luben Tuikov
2006-03-03 10:14 ` Luben Tuikov
2006-03-03 15:23   ` James Bottomley
2006-03-03 15:58     ` Stefan Richter
2006-03-03 16:26       ` James Bottomley
2006-03-03 17:03         ` Mike Anderson
2006-03-03 17:28           ` Jeff Garzik
2006-03-06 18:30       ` Douglas Gilbert
2006-03-03 18:20     ` Luben Tuikov
2006-03-06  8:26 ` Mike Anderson [this message]
2006-03-06 15:13   ` James Bottomley
2006-03-06 16:37     ` Jeff Garzik
2006-03-18  1:45 ` [PATCH] " Alexis Bruemmer
2006-03-18  2:05   ` Alexis Bruemmer
2006-03-18 15:24   ` James Bottomley
2006-03-20  5:53     ` Mike Anderson
  -- strict thread matches above, loose matches on Subject: below --
2006-03-03 16:39 [RFC] " Robert Tarte
2006-03-04  3:01 Tarte, Robert
2006-03-04  4:09 ` James Bottomley
2006-03-04  8:50   ` Luben Tuikov
2006-03-06 19:35   ` Mike Anderson
2006-03-06 19:50     ` James Bottomley
2006-03-07  0:44       ` Alexis Bruemmer
2006-03-08 15:15         ` James Bottomley
2006-03-09 17:06           ` Alexis Bruemmer
2006-03-09 18:05             ` Mike Anderson

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=20060306082614.GA27603@us.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Robert_Tarte@adaptec.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;
as well as URLs for NNTP newsgroup(s).