On Thu, 2010-03-04 at 11:50 +0100, Jon Severinsson wrote: > Hello > > Early this weak I sent a patch implementing posix acl permission checking in > the linux cifs filesystem module. Unfortunately I only sent it to linux-fsdev > as I was unaware of the linux-cifs-client list. I later tried to submit it to > linux-cifs-client as well, but my message seems to have been lost in the > moderation queue, so I subscribed and am trying again. > > I don't believe my patch is perfect, but I think it's a good start, and would > like some comments from more experienced cifs developers to be able to get it > into shape for inclusion in the kernel. > > I did get some comments from Matthew Wilcox at linux-fsdev, but unfortunately > he never followed up on my response, so I'm including some unresolved > questions I still have, as well as attaching the patch for further comments. Hi Jon, although you did a good job with the code itself, I have to say that I think the approach is just wrong. Checking ACLs on the client is simply the wrong way to go. It is just racy and it is not authoritative anyway. It is like trying to look up a path using a cached directory listing and then try to open by inode. It simply doesn't work, by the time you do that, things may have been completely changed on the server. And we are not counting the problem that with CIFS (and samba in particular) the client have no way to know what are the real credentials assigned to the session and that the client may have no idea what the users and groups in the ACL are (if client and server do not use exactly the same user database). The right way is to let the server enforce ACLs, and use multisessions mounts if multiple users are involved. Time would be better spent working in that direction IMO. Simo. -- Simo Sorce Samba Team GPL Compliance Officer <simo@xxxxxxxxx> Principal Software Engineer at Red Hat, Inc. <simo@xxxxxxxxxx> -- 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
