[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080526164858.GA24098@elte.hu>
Date: Mon, 26 May 2008 18:48:58 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Jan Kara <jack@...e.cz>
Cc: Theodore Tso <tytso@....edu>,
Arjan van de Ven <arjan@...ux.intel.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg KH <greg@...ah.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Top 10 bugs/warnings for the week of March 23rd, 2008
* Jan Kara <jack@...e.cz> wrote:
> just fine, as far as I understand. It only spits a dangerously looking
> warning and that's it. I agree we shouldn't be doing this but I don't
> really find this a critical problem.
yeah i know it's "just" a warning, i checked the stack dump on
kerneloops.org before i wrote the mail.
Pulling removable media out while it might still be mounted is a fact of
life and comes not from the stupidity of the user but from the lack of
physical barriers on the device side.
What if the USB stick was pulled mistakenly, the user notices her
mistake later on and plugs the USB stick back in and expects all the
data to not be corrupted?
What if the user puts the stick back in and it wont be mounted or will
be critically damaged?
How do we even know whether these cases all work 100% robustly if the
attitude is that removing a mounted device is a stupid thing to do and a
bug related to it gets deprioritized? [starting with the issue of why
the user should even care about such a relatively low-level abstraction
as a "mounted filesystem".]
And any such problems do come up in the enterprise space as well, in
terms of multipath IO issues - and Linux still does quite poorly in that
area.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists