From: Xavier Bestel <xavier.bestel@free.fr>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andries Brouwer <aebr@win.tue.nl>, Greg KH <greg@kroah.com>,
Andrey Borzenkov <arvidjaar@mail.ru>,
linux-hotplug-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: removable media revalidation - udev vs. devfs or static /dev
Date: Thu, 08 Jan 2004 08:00:41 +0000 [thread overview]
Message-ID: <1073548840.6189.144.camel@nomade> (raw)
In-Reply-To: <Pine.LNX.4.58.0401071941390.2131@home.osdl.org>
Le jeu 08/01/2004 à 04:43, Linus Torvalds a écrit :
> On Thu, 8 Jan 2004, Andries Brouwer wrote:
> >
> > I am even happy in a somewhat more general situation that you are.
> > If the kernel autopartitions (and make recognition of new partitions
> > hotplug events so that udev can create the device nodes), all is well.
>
> Yes. We _could_ do that, by just making a "we noticed the disk change" be
> a hotplug event. However, I'm loath to do that, because some devices
> literally don't even have an easily read disk change signal, so what they
> do is
>
> - assume the disk _always_ changed on open
> - do a quick IO to verify it
>
> and I'd be nervous about that kind of thing resulting in hotplug being
> called constantly if somebody rude just has an endless loop of
> "open()/close()".
Theses devices are kind of broken anyway, aren't they ? I see no safe
way of handling disk changes on them, except having a "I changed disk in
this drive" button on the desktop and rely on the user's good behavior.
Currently the kernel will may have a wrong idea of what's in the drive
if it doesn't poll, and that may wreak havoc.
Xav
-------------------------------------------------------
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
WARNING: multiple messages have this Message-ID (diff)
From: Xavier Bestel <xavier.bestel@free.fr>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andries Brouwer <aebr@win.tue.nl>, Greg KH <greg@kroah.com>,
Andrey Borzenkov <arvidjaar@mail.ru>,
linux-hotplug-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: removable media revalidation - udev vs. devfs or static /dev
Date: Thu, 08 Jan 2004 09:00:41 +0100 [thread overview]
Message-ID: <1073548840.6189.144.camel@nomade> (raw)
In-Reply-To: <Pine.LNX.4.58.0401071941390.2131@home.osdl.org>
Le jeu 08/01/2004 à 04:43, Linus Torvalds a écrit :
> On Thu, 8 Jan 2004, Andries Brouwer wrote:
> >
> > I am even happy in a somewhat more general situation that you are.
> > If the kernel autopartitions (and make recognition of new partitions
> > hotplug events so that udev can create the device nodes), all is well.
>
> Yes. We _could_ do that, by just making a "we noticed the disk change" be
> a hotplug event. However, I'm loath to do that, because some devices
> literally don't even have an easily read disk change signal, so what they
> do is
>
> - assume the disk _always_ changed on open
> - do a quick IO to verify it
>
> and I'd be nervous about that kind of thing resulting in hotplug being
> called constantly if somebody rude just has an endless loop of
> "open()/close()".
Theses devices are kind of broken anyway, aren't they ? I see no safe
way of handling disk changes on them, except having a "I changed disk in
this drive" button on the desktop and rely on the user's good behavior.
Currently the kernel will may have a wrong idea of what's in the drive
if it doesn't poll, and that may wreak havoc.
Xav
next prev parent reply other threads:[~2004-01-08 8:00 UTC|newest]
Thread overview: 131+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 20:33 removable media revalidation - udev vs. devfs or static /dev Andrey Borzenkov
2004-01-01 20:33 ` Andrey Borzenkov
2004-01-03 5:58 ` Greg KH
2004-01-03 5:58 ` Greg KH
2004-01-03 8:51 ` Andrey Borzenkov
2004-01-03 8:51 ` Andrey Borzenkov
2004-01-03 12:37 ` Andries Brouwer
2004-01-03 12:37 ` Andries Brouwer
2004-01-03 12:42 ` Olaf Hering
2004-01-03 12:42 ` Olaf Hering
2004-01-03 16:05 ` Andrey Borzenkov
2004-01-03 16:05 ` Andrey Borzenkov
2004-01-03 17:54 ` Jens Axboe
2004-01-03 17:54 ` Jens Axboe
2004-01-07 9:43 ` Olaf Hering
2004-01-07 9:43 ` Olaf Hering
2004-01-07 9:50 ` Jens Axboe
2004-01-07 9:50 ` Jens Axboe
2004-01-07 9:56 ` Olaf Hering
2004-01-07 9:56 ` Olaf Hering
2004-01-07 9:59 ` Jens Axboe
2004-01-07 9:59 ` Jens Axboe
2004-01-07 10:25 ` Olaf Hering
2004-01-07 10:25 ` Olaf Hering
2004-01-07 10:31 ` Jens Axboe
2004-01-07 10:31 ` Jens Axboe
2004-01-07 10:47 ` Andrey Borzenkov
2004-01-07 10:47 ` Andrey Borzenkov
2004-01-07 10:54 ` Jens Axboe
2004-01-07 10:54 ` Jens Axboe
2004-01-07 17:56 ` Greg KH
2004-01-07 17:56 ` Greg KH
2004-01-30 12:59 ` Olaf Hering
2004-01-30 12:59 ` Olaf Hering
2004-01-07 11:00 ` Andrey Borzenkov
2004-01-07 11:00 ` Andrey Borzenkov
2004-01-07 11:05 ` Jens Axboe
2004-01-07 11:05 ` Jens Axboe
2004-01-07 11:14 ` Andrey Borzenkov
2004-01-07 11:14 ` Andrey Borzenkov
2004-01-07 11:16 ` Jens Axboe
2004-01-07 11:16 ` Jens Axboe
2004-01-03 20:51 ` Greg KH
2004-01-03 20:51 ` Greg KH
2004-01-07 18:38 ` Linus Torvalds
2004-01-07 18:38 ` Linus Torvalds
2004-01-07 18:57 ` Greg KH
2004-01-07 18:57 ` Greg KH
2004-01-07 19:23 ` Mika Penttilä
2004-01-07 19:23 ` Mika Penttilä
2004-01-07 19:24 ` Greg KH
2004-01-07 19:24 ` Greg KH
2004-01-07 19:31 ` Mika Penttilä
2004-01-07 19:31 ` Mika Penttilä
2004-01-08 1:38 ` Linus Torvalds
2004-01-08 1:38 ` Linus Torvalds
2004-01-07 19:31 ` Linus Torvalds
2004-01-07 19:31 ` Linus Torvalds
2004-01-07 19:50 ` Greg KH
2004-01-07 19:50 ` Greg KH
2004-01-07 20:25 ` Richard Troth
2004-01-07 20:25 ` Richard Troth
2004-01-07 20:38 ` Valdis.Kletnieks
2004-01-07 23:34 ` Greg KH
2004-01-07 23:34 ` Greg KH
2004-01-08 0:32 ` Martin J. Bligh
2004-01-08 0:32 ` Martin J. Bligh
2004-01-08 0:41 ` Greg KH
2004-01-08 0:41 ` Greg KH
2004-01-08 1:07 ` Martin J. Bligh
2004-01-08 1:07 ` Martin J. Bligh
2004-01-08 1:15 ` Greg KH
2004-01-08 1:15 ` Greg KH
2004-01-08 1:50 ` Martin J. Bligh
2004-01-08 1:50 ` Martin J. Bligh
2004-01-08 18:34 ` Martin Schlemmer
2004-01-08 1:48 ` Linus Torvalds
2004-01-08 1:48 ` Linus Torvalds
2004-01-08 0:42 ` viro
2004-01-08 0:42 ` viro
2004-01-08 1:16 ` Greg KH
2004-01-08 1:16 ` Greg KH
2004-01-09 3:36 ` Joel Becker
2004-01-09 3:36 ` Joel Becker
2004-01-09 9:49 ` Gerd Knorr
2004-01-12 17:16 ` Joel Becker
2004-01-12 23:08 ` J.A. Magallon
2004-01-07 20:52 ` Olaf Hering
2004-01-07 20:52 ` Olaf Hering
2004-01-08 2:03 ` Linus Torvalds
2004-01-08 2:03 ` Linus Torvalds
2004-01-08 4:16 ` Gene Heskett
2004-01-08 4:16 ` Gene Heskett
2004-01-08 4:23 ` Linus Torvalds
2004-01-08 4:23 ` Linus Torvalds
2004-01-08 7:45 ` Olaf Hering
2004-01-08 7:45 ` Olaf Hering
2004-01-08 2:13 ` Andries Brouwer
2004-01-08 2:13 ` Andries Brouwer
2004-01-08 2:19 ` Linus Torvalds
2004-01-08 2:19 ` Linus Torvalds
2004-01-08 2:49 ` Andries Brouwer
2004-01-08 2:49 ` Andries Brouwer
2004-01-08 2:56 ` Linus Torvalds
2004-01-08 2:56 ` Linus Torvalds
2004-01-08 3:35 ` Andries Brouwer
2004-01-08 3:35 ` Andries Brouwer
2004-01-08 3:43 ` Linus Torvalds
2004-01-08 3:43 ` Linus Torvalds
2004-01-08 8:00 ` Xavier Bestel [this message]
2004-01-08 8:00 ` Xavier Bestel
2004-01-09 0:28 ` Robert Love
2004-01-09 0:28 ` Robert Love
2004-01-09 0:52 ` Linus Torvalds
2004-01-09 0:52 ` Linus Torvalds
2004-01-09 1:16 ` Matt Mackall
2004-01-09 1:16 ` Matt Mackall
2004-01-08 10:32 ` Éric Brunet
2004-01-08 14:06 ` "Andrey Borzenkov"
2004-01-08 14:06 ` "Andrey Borzenkov"
2004-01-12 9:09 ` Ling, Xiaofeng
2004-01-12 9:09 ` Ling, Xiaofeng
2004-03-29 15:39 ` Greg KH
2004-03-29 15:39 ` Andrey Borzenkov
2004-03-29 15:40 ` Andries Brouwer
2004-03-29 15:40 ` Olaf Hering
2004-03-29 15:40 ` Andrey Borzenkov
2004-03-29 15:40 ` Jens Axboe
2004-03-29 15:40 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 5:19 Iqbal
2004-01-12 13:02 Nicolas Mailhot
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=1073548840.6189.144.camel@nomade \
--to=xavier.bestel@free.fr \
--cc=aebr@win.tue.nl \
--cc=arvidjaar@mail.ru \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.