From: Mike Anderson <andmike@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: "Infante, Jon" <Jon.Infante@Emulex.Com>,
Martin Peschke3 <MPESCHKE@de.ibm.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: How to resurrect offlined SCSI devices?
Date: Wed, 26 May 2004 11:02:53 -0700 [thread overview]
Message-ID: <20040526180253.GB1561@us.ibm.com> (raw)
In-Reply-To: <1085593035.2116.539.camel@mulgrave>
James Bottomley [James.Bottomley@SteelEye.com] wrote:
> Not necessarily roll our own, just plug into the hotplug
> infrastructure. But generate events, definitely.
Yes we do not need to roll our own, Mike C's mail pointed out that these
interfaces are exported.
We should be able to add a call to kobject_hotplug in
scsi_device_set_state for certain / all state transitions depending on
how many events one would want to go to users space. Unexpected state
transitions would seem like a good starting point to not generate to
much user space traffic (i.e running -> offline, offline -> running).
This also assumes that if one expects user space reaction to these
events occurring on a root device they have already prepared there needed
tools in a ramdisk environment.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2004-05-26 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 16:17 How to resurrect offlined SCSI devices? Infante, Jon
2004-05-26 16:55 ` James Bottomley
2004-05-26 17:15 ` Mike Anderson
2004-05-26 17:26 ` Mike Christie
2004-05-26 17:48 ` Mike Anderson
2004-05-26 17:37 ` James Bottomley
2004-05-26 18:02 ` Mike Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-27 20:05 Martin Peschke3
2004-05-27 20:04 Martin Peschke3
2004-05-26 16:48 Salyzyn, Mark
2004-05-26 15:04 Martin Peschke3
2004-05-26 15:11 ` James Bottomley
2004-05-26 13:14 Martin Peschke3
2004-05-26 14:45 ` 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=20040526180253.GB1561@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=Jon.Infante@Emulex.Com \
--cc=MPESCHKE@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.