From: Alexis Bruemmer <alexisb@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] aic94xx: Hotplug ex_change_count race fix
Date: Tue, 03 Oct 2006 08:30:12 -0700 [thread overview]
Message-ID: <1159889413.7024.15.camel@localhost.localdomain> (raw)
In-Reply-To: <1159885160.3443.20.camel@mulgrave.il.steeleye.com>
On Tue, 2006-10-03 at 09:19 -0500, James Bottomley wrote:
> On Tue, 2006-09-26 at 15:05 -0700, Alexis Bruemmer wrote:
> > In some cases while hotplugging disks on a system with an expander the
> > broadcast primitive will be posted and begin processing before the
> > expander change count is updated. This causes the device that triggered
> > the broadcast to not be found.
>
> Thanks; I'll stick this in.
>
> However, it has always struck me that this broadcast code is fragile
> because of the way event processing works. If we get two fairly close
> together broadcast events, we'll amalgamate them into a single event and
> then stop processing as soon as we find one expander that changed, if
> you want to look at sorting that out ...
I will look into it.
--Alexis
>
> James
>
>
next prev parent reply other threads:[~2006-10-03 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 22:05 [PATCH] aic94xx: Hotplug ex_change_count race fix Alexis Bruemmer
2006-10-03 14:19 ` James Bottomley
2006-10-03 15:30 ` Alexis Bruemmer [this message]
2006-10-04 23:52 ` malahal
2006-10-03 20:52 ` Luben Tuikov
2006-10-03 21:18 ` Jeff Garzik
2006-10-04 2:29 ` Douglas Gilbert
2006-10-04 7:39 ` Luben Tuikov
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=1159889413.7024.15.camel@localhost.localdomain \
--to=alexisb@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