public inbox for linux-scsi@vger.kernel.org
 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>
Subject: Re: aic94xx panic on module insertion
Date: Mon, 10 Jul 2006 21:52:06 -0700	[thread overview]
Message-ID: <20060711045206.GA7552@us.ibm.com> (raw)
In-Reply-To: <1152565651.4027.11.camel@mulgrave.il.steeleye.com>

James Bottomley <James.Bottomley@SteelEye.com> wrote:
> On Mon, 2006-07-10 at 10:29 -0700, Mike Anderson wrote:
> > Yes, since we have not formed a port yet on phy1 it would appear that we
> > could just drop this event if port is null as we are going to do discovery
> > post port forming the port anyway.
> 
> OK, so this is the fix?
> 
> James
> 
> diff --git a/drivers/scsi/sas/sas_port.c b/drivers/scsi/sas/sas_port.c
> index 07415e9..d931478 100644
> --- a/drivers/scsi/sas/sas_port.c
> +++ b/drivers/scsi/sas/sas_port.c
> @@ -199,6 +199,12 @@ void sas_porte_broadcast_rcvd(void *data
>  	u32 prim;
>  	struct asd_sas_phy *phy = data;
>  
> +	/* Broadcast received before port forms.  This is fine, since
> +	 * port formation will trigger a domain discovery (rather than
> +	 * revalidation) */
> +	if (!sas->port)
> +		return;
> +
>  	sas_begin_event(PORTE_BROADCAST_RCVD, &phy->ha->event_lock,
>  			&phy->port_events_pending);
>  

or this is the one I was trying, but I cannot generate the events you
where seeing. I was trying to create fake ones but have not been
successful. Either seems like it would address this event.

Index: aic94xx-sas-2.6-patched/drivers/scsi/sas/sas_discover.c
===================================================================
--- aic94xx-sas-2.6-patched.orig/drivers/scsi/sas/sas_discover.c	2006-07-10 11:56:43.000000000 -0700
+++ aic94xx-sas-2.6-patched/drivers/scsi/sas/sas_discover.c	2006-07-10 15:58:44.000000000 -0700
@@ -717,7 +717,11 @@ static void sas_revalidate_domain(void *
 
 int sas_discover_event(struct asd_sas_port *port, enum discover_event ev)
 {
-	struct sas_discovery *disc = &port->disc;
+	struct sas_discovery *disc;
+
+	if (!port)
+		return;
+	disc = &port->disc;
 
 	BUG_ON(ev >= DISC_NUM_EVENTS);
 
-andmike
--
Michael Anderson
andmike@us.ibm.com

  reply	other threads:[~2006-07-11  4:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 14:22 aic94xx panic on module insertion James Bottomley
2006-07-10 16:25 ` Douglas Gilbert
2006-07-10 16:40   ` James Bottomley
2006-07-10 17:08     ` Mike Anderson
2006-07-10 21:18       ` James Bottomley
2006-07-10 17:29 ` Mike Anderson
2006-07-10 21:07   ` James Bottomley
2006-07-11  4:52     ` Mike Anderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-11  8:05 Robert Tarte

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=20060711045206.GA7552@us.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@SteelEye.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