lkml.org 
[lkml]   [2005]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 12/18] shared mount handling: bind and rbind
From
Date
> No. As explained in the same earlier threads; without this change the
> behavior of shared-subtrees leads to inconsistency and confusion in some
> scenarios.
>
> Under the premise that no application should depend on this behavior
> (most-recent-mount-visible v/s top-most-mount-visible),

The strongest argument against was that

mount foo .; umount .

would no longer be a no-op.

> Al Viro permitted this change. And this is certainly the right
> behavior.

Which is a contradiction in term, since you are saying that
applications _do_ depend on it.

Miklos
-
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/

\
 
 \ /
  Last update: 2005-11-08 16:58    [W:0.076 / U:0.272 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site