Re: silent semantic changes with reiser4

From: viro
Date: Thu Aug 26 2004 - 15:59:45 EST


On Thu, Aug 26, 2004 at 08:13:23PM +0100, viro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:

> Hey, if we lose the "can't unlink/rmdir/rename over something that is
> a mountpoint in other life" - I'm happy and we can get a lot of much
> more interesting stuff to work. It will take some work (e.g. making
> sure we can find all vfsmounts over given mountpoint and sorting out
> the locking issues, which won't be trivial), but the main obstacle in
> that direction is not in architecture - it's in SuS and tradition; as
> the matter of fact, our life would be much easier if we stopped trying
> to give -EBUSY here and just dissolved all subtrees mounted on anything
> that has that dentry.

Argh... OK, now I remember why I went for -EBUSY for unlink() (we obviously
are not bound by SuS on that one). Consider the following scenario:
* local file foo got something else bound on it for a while
* we are tight on space - time to clean up
* oh, look - contents of foo is junk
* rm foo
* ... oh, fuck, there goes the underlying file.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/