On Mon, Jan 12, 2026 at 12:46:13PM -0500, Chuck Lever wrote: > From: Chuck Lever <[email protected]> > > Following on from > > https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa > > I'm attempting to implement enough support in the Linux VFS to > enable file services like NFSD and ksmbd (and user space > equivalents) to provide the actual status of case folding support > in local file systems. The default behavior for local file systems > not explicitly supported in this series is to reflect the usual > POSIX behaviors: > > case-insensitive = false > case-preserving = true > > The case-insensitivity and case-preserving booleans can be consumed > immediately by NFSD. These two booleans have been part of the NFSv3 > and NFSv4 protocols for decades, in order to support NFS clients on > non-POSIX systems. > > Support for user space file servers is why this series exposes case > folding information via a user-space API. I don't know of any other > category of user-space application that requires access to case > folding info.
This all looks good to me. Just one question: This reads like you are exposing the new file attr bits via userspace but I can only see changes to the kernel internal headers not the uapi headers. So are you intentionally not exposing this as a new uapi extension to file attr or is this an accident? _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
