From: linas@austin.ibm.com
To: linux-hotplug@vger.kernel.org
Subject: Re: unclean yanking out of device?
Date: Wed, 14 Jan 2004 23:08:49 +0000 [thread overview]
Message-ID: <20040114170849.I57254@forte.austin.ibm.com> (raw)
In-Reply-To: <20040114160002.G57254@forte.austin.ibm.com>
On Wed, Jan 14, 2004 at 02:19:21PM -0800, Greg KH wrote:
> On Wed, Jan 14, 2004 at 04:00:02PM -0600, linas@austin.ibm.com wrote:
> >
> > What is supposed to happen if I just yank out a (network/scsi) device
> > while it is being used, without calling any of the hotplug unregister
> > remove etc. functions in advance?
>
> Depends on the driver, device type, subsystem type, and most
> importantly, the kernel version (2.2?, 2.4?, 2.6?)
>
> This is better asked on the linux-kernel mailing list, with a specific
> and detailed question, as you have asked a very broad one.
Sorry, this was intentionally a broad question; I'm hoping to hash
out a broad answer here before I go lkml.
Let me rephrase: I want to make 'appropriate' changes to the 2.6/2.7
kernel, and some selected device drivers, so that a sysadmin can
stupidly yank out an *ordinary* PCI card (not a pcmcia) without doing
an orderly shutdown in advance.
More specifically, I have a whiz-bang PCI controller that will
shut down a PCI slot when it is hit by a cosmic ray (data/address
parity error, other error, etc.). I want to be able to "recover"
that slot, (if its recoverable), and get things going again.
I'm kind-of on day 2 of thinking about this problem, and as far
as I've gotten is thinking that some of the hot-plug infrastructure
might be useful in doing this. I've also noticed that include/linux/pci.h
struct pci_driver doesn't have a "remove_because_your_hardware's_already_gone"
callback, and it seems to me that this kind of callback would be needed.
So I'm sort of trolling to find out if this kind of a problem
has been discussed before, and for other interested parties
to discuss it with.
--linas
p.s. yes, I know the broad reprecussions something like this can have.
I have noticed, for instance, that if you unplug a hot scsi cable,
that reiserfs3 panic's, whereas ext3 seems to deal with it nicely.
I'm hoping to slowly start dealing with the broader implications ...
eventually.
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-01-14 23:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 22:00 unclean yanking out of device? linas
2004-01-14 22:15 ` Måns Rullgård
2004-01-14 22:19 ` Greg KH
2004-01-14 23:08 ` linas [this message]
2004-01-14 23:24 ` Greg KH
2004-01-14 23:49 ` Paul Ionescu
2004-01-14 23:57 ` linas
2004-01-15 0:19 ` Oliver Neukum
2004-01-15 0:19 ` Greg KH
2004-01-15 0:34 ` Greg KH
2004-01-15 0:36 ` David Brownell
2004-01-15 1:16 ` linas
2004-01-15 1:20 ` linas
2004-01-15 1:33 ` Greg KH
2004-01-15 1:35 ` Greg KH
2004-01-15 1:57 ` linas
2004-01-15 17:17 ` Richard Troth
2004-01-15 18:38 ` linas
2004-01-15 21:22 ` David Hinds
2004-01-24 0:38 ` Greg KH
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=20040114170849.I57254@forte.austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linux-hotplug@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).