On Sat, Dec 26, 2015 at 07:11:16PM -0500, Trond Myklebust wrote: > Ah... IOW: That so called "fast path" crap in do_last() is screwing us > over by forcing us to to 2 ACCESS calls. The first being done for no > good reason by the VFS, and the second being done in the OPEN call to > the server in the NFS client. Excuse me, but this is complete BS. First of all, are you suggesting that every filesystem out there must push the permission checks into its ->open()? This may_open() is where they normally happen... Moreover, the things like "this mount is r/o, don't let anything to be opened on it" are inherently client-side. It's a property of vfsmount; the same fs instance might be accessible r/w in another place. And things like opening a device node, etc. are not reaching the server at all. > > Merry Christmas > > Suggestions Al? Make nfs_permission() relax the checks when it sees MAY_OPEN, if you know that things will be caught by server anyway? -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
