From: Ingo Molnar <mingo@elte.hu>
To: Theodore Tso <tytso@mit.edu>,
Arjan van de Ven <arjan@linux.intel.com>, Jan Kara <jack@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Top 10 bugs/warnings for the week of March 23rd, 2008
Date: Mon, 26 May 2008 12:48:32 +0200 [thread overview]
Message-ID: <20080526104832.GG23261@elte.hu> (raw)
In-Reply-To: <20080526101646.GD24507@mit.edu>
* Theodore Tso <tytso@MIT.EDU> wrote:
> On Mon, May 26, 2008 at 11:39:13AM +0200, Ingo Molnar wrote:
> > Exactly why is pulling an USB stick considered "stupid"? Last i checked
> > there was no physical lock preventing users from doing that.
> >
> > Sure, pulling a mounted USB stick is inconvenient ... for _us_
> > kernel developers. But the user really doesnt care and shouldnt
> > care.
>
> Because they could lose data? Because if the kernel wakes up and
> tries writing to the USB stick right as they pull it out, it could
> physically damage the flash format? I know, stupid reason... :-)
user can lose data in many other ways, that's not the issue - the issue
here is something very crutial: the kernel gets confused about a _very_
common user-triggerable condition.
That confusion must not happen in a modern OS and the kernel should be
resilient and cope with such external events. And we must not
deprioritize it with an incorrect "user did something stupid" tag...
That argument might have been valid 15 years ago when floppies could be
locked and you needed a needle to force-eject it but it is rather lame
today when unplugging an USB stick is as easy as moving the mouse.
If there's something stupid here it's the kernel not dealing with that
condition properly. Yes, the "user action" here looks "trivial" to the
user but what happens below is indeed very hard technically, but who
said that writing an OS from scratch would be an easy task? ;-)
Ingo
next prev parent reply other threads:[~2008-05-26 10:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 16:19 Top 10 bugs/warnings for the week of March 23rd, 2008 Arjan van de Ven
2008-05-23 16:23 ` Top 10 bugs/warnings for the week of May " Arjan van de Ven
2008-05-23 16:42 ` Top 10 bugs/warnings for the week of March " Linus Torvalds
2008-05-23 17:35 ` Arjan van de Ven
2008-05-23 19:31 ` Alan Cox
2008-05-24 0:15 ` Chris Wright
2008-05-24 5:07 ` Arjan van de Ven
2008-05-26 9:36 ` Ingo Molnar
2008-05-24 5:32 ` Greg KH
2008-05-24 22:23 ` Jan Kara
2008-05-24 22:30 ` Arjan van de Ven
2008-05-24 22:45 ` Theodore Tso
2008-05-25 11:58 ` Stefan Richter
2008-05-26 9:39 ` Ingo Molnar
2008-05-26 10:16 ` Theodore Tso
2008-05-26 10:48 ` Ingo Molnar [this message]
2008-05-26 16:20 ` Jan Kara
2008-05-26 16:48 ` Ingo Molnar
2008-05-26 17:01 ` Theodore Tso
2008-05-26 17:09 ` Oliver Neukum
2008-05-26 17:28 ` Bart Van Assche
2008-05-26 17:38 ` Jan Kara
2008-05-26 17:50 ` Theodore Tso
2008-05-26 18:23 ` Ingo Molnar
2008-05-27 6:12 ` Oliver Neukum
2008-05-27 11:41 ` Pavel Machek
2008-05-27 3:49 ` Greg KH
2008-05-27 11:40 ` Pavel Machek
2008-05-26 14:52 ` Stefan Richter
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=20080526104832.GG23261@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=greg@kroah.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.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