01.12.2013 17:14, Christoph Hellwig пишет:
As-is this has one major downside: because the initial mount already grabs a reference to the network namespace we'll create a cyclic reference and will never free the network namespace. To get around this we'd need some way to only grab it once user mounts show up / disapear in the VFS.
That's a great cleanup of the whole PipeFS mount/umount logic. And it actually moves code to the state it was (with minor changes) before net namespace changes. But the reason for all this "damage" was exactly to remove this major downside and do _not_ tie network namespace to mount point.. So, please, solve the problem before reverting all this notifiers and friends. -- Best regards, Stanislav Kinsbursky -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
