On Fri, Apr 09, 2021 at 06:24:21PM +0200, Christian Brauner wrote: > Reading through the codebase of ecryptfs it currently takes path->mnt > and then retrieves that path whenever it needs to perform operations in > the underlying filesystem. Simply drop the old path->mnt once we've > created a private mount and place the new private mnt into path->mnt. > This should be all that is needed to make this work since ecryptfs uses > the same lower path's vfsmount to construct the paths it uses to operate > on the underlying filesystem. > + mnt = clone_private_mount(&path); Incidentally, why is that thing anything other than a trivial wrapper for mnt_clone_internal() (if that - I'm not convinced that the check of unbindable is the right thing to do here). Miklos?
