Christian Brauner <brauner@xxxxxxxxxx> wrote: > > > It also uses the lookup_one_len() family of functions which implicitly > > > use &nop_mnt_idmap. This mixture of implicit and explicit could be > > > confusing. When we eventually update cachefiles to support idmap mounts > > > it > > > > Is that something we ever plan to do? > > It should be pretty easy to do. I just didn't see a reason to do it yet. > > Fwiw, the cache paths that cachefiles uses aren't private mounts like > overlayfs does it, i.e., cachefiles doesn't do clone_private_mount() before > stashing cache->mnt. ... This is probably something cachefilesd needs to do in userspace before telling the kernel through /dev/cachefiles where to find the cache. David
