Messages in this thread |  | | Date | Mon, 17 Sep 2001 04:38:59 -0400 (EDT) | From | Alexander Viro <> | Subject | Re: Forced umount (was lazy umount) |
| |
On Mon, 17 Sep 2001, Aaron Lehmann wrote:
> On Mon, Sep 17, 2001 at 09:57:47AM +0300, Ville Herva wrote: > > > Basically, I want a 'kill -KILL' for filesystems. > > > > This gets my vote too... > > <aol>Me too</aol>
Look at it that way: we have two actions that need to be done upon umount. 1) detach it from the mountpoint(s) 2) shut it down
For the latter we need to have no active IO on that fs _and_ nothing that could initiate such IO. We can separate #1 and #2, letting fs shutdown happen when it's no longer busy. That's what MNT_DETACH does.
What you are asking for is different - you want fs-wide revoke(). That's all nice and dandy, but it's an independent problem and it will take a _lot_ of work. Including work in fs drivers. It _is_ worth doing, but it's 2.5 stuff (along with normal revoke(2)).
IMNSHO we really should separate the stuff acting on mount tree from the stuff acting on filesystems. A lot of confusion comes from the places where we don't do that - see the "per-mountpoint read-only" thread couple of weeks ago for other examples.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |