On Mon, 2014-03-03 at 10:40 +0800, Ian Kent wrote: > > > > > That doesn't solve the problem, however, that mounts cloned by a > > unshare(CLONE_NEWNS) would never expire. Also there is another bug > > somewhere, because I see, that the mount, visible to the > > /usr/lib/colord/colord process was logged as "unmounted" in the nfs > > server when it expired in the global namespace. So I doubt it would be > > working even for that process. So possibly automounted mounts shouldn't > > be cloned at all? Together with chroot or pivot_root the sematics would > > be more than unclear anyway. Your problem now :-) > > Hehe, like I said some people are going to be disappointed. > > There's just one question about this that remains. > > Assuming systemd is setting "/" shared what happens if "mount > --make-rprivate /" is run before autofs is started? > > So if you can spend a little more time on this an answer to this would > be helpful. No need for this, thanks to your reproducer. In fact the problem doesn't appear happen if "/" is set shared so in your case "/" must be set either slave or private. And expanding the reproducer a bit I see another failure case too, and it doesn't appear to be the unreliable d_mountpoint() check, not sure yet exactly what it is. Thanks Ian -- To unsubscribe from this list: send the line "unsubscribe autofs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
