On 2017/3/30 15:03, Amir Goldstein wrote: >> Hi: >> Current overlayfs does not support underlying filesystem which have "weird" d_flags (like DCACHE_OP_HASH， >> DCACHE_OP_COMPARE, DCACHE_OP_REVALIDATE, etc). So we cannot support fs have it's own d_hash, d_compare and >> d_revalidate functions. > > Not accurate. d_revalidate() is allowed for lower, but not for upper > (ovl_dentry_remote()). > Thank you for the corrections, I see it in the ovl_lower_dir(). >> >> Do you have a TODO plan to support it in a future version ? >> > > Which of the constrains is relevant to your use case? (which of the flags) > Do you need it for lower / upper or both? > Is it a proprietary file system of a known one you need to support? > We want to use d_hash(), d_compare() and d_revalidate() to our own proprietary file system (not a remote fs, not widely used, and it's file name is case-insensitive) for lower and upper both, and we also need to use d_revalidate() to do some special handling. I see there were many other rarely used（?）file systems also use d_hash(), d_compare(), d_revalidate() in kernel(such as hfs, jfs, fat, etc.), they are also not supportted by ovlfs. So I would like to know are these file systems need to support in future ? Thanks, ZhangYi. -- 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
