Thanks. That could help in the short-term. I'd hope to see see this in mainline eventually. If someone could elaborate on the blanket exclusion of d_revalidate, I'd like to see if the task to add read-only NFS support is reasonable. -Blake On Feb 9, 2015, at 2:12 PM, Eric Jones <ejones@xxxxxxxx> wrote: > I don't have an answer, but I'll note it worked at some point. For example, the overlayfs code in SuSE's SLES12 release allows it. I'm not sure why Novell merged such a different version of the overlayfs code. > > > On Mon, Feb 09, 2015 at 03:11:46PM +0000, Caldwell, Blake A. wrote: >> Hi there, >> >> Is perhaps a fix for disabling overlayfsroot for filesystems with revalidate on the horizon? My use case for overlayfs is a NFS (v3 or v4) lowerdir, which appears rejected by the code below because NFS defines d_revalidate, d_automount, and d_weak_revalidate (v3 only). >> >> There has been discussion in this launchpad bug about xattr copyup problems: >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039402 >> >> fs/overlayfs/super.c@692: >> /* >> * We don't support: >> * - automount filesystems >> * - filesystems with revalidate (FIXME for lower layer) >> * - filesystems with case insensitive names >> */ >> if (dop && >> (dop->d_manage || dop->d_automount || >> dop->d_revalidate || dop->d_weak_revalidate || >> dop->d_compare || dop->d_hash)) { >> return false; >> } >> >> Regarding the referenced code in overlayfs-next, is there a condition in which NFSv4 could be supported, such as if mounted read-only? >> >> -Blake >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
