From: Andries Brouwer <aebr@win.tue.nl>
To: Matthew Jacob <mjacob@feral.com>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
"Cress, Andrew R" <andrew.r.cress@intel.com>,
andmike@us.ibm.com, David Brownell <david-b@pacbell.net>,
Greg KH <greg@kroah.com>,
Linux SCSI list <linux-scsi@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net,
Luben Tuikov <luben@splentec.com>,
Matthew Dharm <mdharm-scsi@one-eyed-alien.net>,
Oliver Neukum <oliver@neukum.name>,
Steven Dake <sdake@mvista.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [linux-usb-devel] RE: A different look at block device hotswap in the Linux kernel
Date: Sun, 26 Jan 2003 12:26:11 +0100 [thread overview]
Message-ID: <20030126112611.GA2814@win.tue.nl> (raw)
In-Reply-To: <20030124100832.Y1605-100000@wonky.in0.lcl>
On Fri, Jan 24, 2003 at 10:09:32AM -0800, Matthew Jacob wrote:
> > It's like when I pull the power plug because my system is totally hosed and
> > I want to start over. I know I can cause damage by doing that, but I would
> > be upset if the new system booted back to the broken state it was in when I
> > unplugged it.
>
> You may want your device to reattach as totally new. You may, on the other
> hand, want your device to resume where you left off. I can see valid
> reasons for wanting either behaviour (but it can't/shouldn't be deduced
> by the OS).
The kernel does not remember this device once it is gone.
If user space thinks it recognizes it, it must have a means to
tell the kernel what it should do. What kind of info?
The only thing that I can think of right now is the name.
User space may tell the kernel under what name a device should
be accessible.
[Today user space can tell the kernel the numbering of the partitions.]
More generally, the question of what "same device" means
depends on the application. Is /dev/fd0 the same device
as /dev/fd0 also when the floppy is different?
Yes, the name is the same. The contents not.
In all cases user space does not tell the kernel "it is the same as ..."
since the kernel does not remember anyway. User space just instructs
the kernel to do certain definite things.
Andries
next prev parent reply other threads:[~2003-01-26 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 16:36 A different look at block device hotswap in the Linux kernel Cress, Andrew R
2003-01-24 18:01 ` Bryan Henderson
2003-01-24 18:09 ` Matthew Jacob
2003-01-26 11:26 ` Andries Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-21 21:02 [linux-usb-devel] Re: [PATCH] USB changes for 2.5.58 Alan Stern
2003-01-23 18:19 ` Oliver Neukum
2003-01-23 20:41 ` A different look at block device hotswap in the Linux kernel Steven Dake
2003-01-24 0:07 ` Oliver Neukum
2003-01-24 0:54 ` Steven Dake
2003-01-24 2:35 ` [linux-usb-devel] " Matthew Dharm
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=20030126112611.GA2814@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=andmike@us.ibm.com \
--cc=andrew.r.cress@intel.com \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=hbryan@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=luben@splentec.com \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=mjacob@feral.com \
--cc=oliver@neukum.name \
--cc=sdake@mvista.com \
--cc=stern@rowland.harvard.edu \
/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