This is a follow-up agenda topic to the similar topic for LSF-2013. The goal if this agenda item is to discuss the current status and to coordinate future work in the area of kernel support for file servers such as Samba and NFS- Ganesha. There is work in process based on discussions at the last meeting that can be reported on. These issues are very important for the NFS-Ganesha project that with its V2.0 release is being used by IBM, Red Hat, Panasas and others as their pNFS server. These topics do not require presentations other than 1 or 2 slides to keep discussion on topic. The goal is to clean up the rough edges and issues of current work and focus on near term goals for work still to be done. Specifics: * New private locks to provide better semantics than Posix locks. Jeff Layton has been working on this. * An extension to inotify() to control event reporting where nfs-ganesha, samba, and local users/processes on the server access the same files. Jim Lieb has been working on this and has submitted a patchset to the list. * Credentials switching to extend nfsd_setuser semantics to user-mode so servers that need to do this operation can use it. There is an implementation that in its current form still has some issues that need to be resolved based on feedback on the list. * readdirplus. This is a carryover from last year. Status unknown but the need is still there. * rich ACLs. Some work has been done but this too needs decisions and work. This is especially important to NFSv4.1 and CIFS server projects. * Discussions with samba developers on strategies/solutions for mapping credentials between NFSv4.x and SMB. I am willing to combine these specific issues with someone else's agenda topic if it makes scheduling simpler. Regards, Jim Lieb -- Jim Lieb Linux Systems Engineer Panasas Inc. "If ease of use was the only requirement, we would all be riding tricycles" - Douglas Engelbart 1925–2013 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
