--- Dave Quigley <dpquigl@xxxxxxxxxxxxx> wrote: > Yea, I didn't get to read the rest of the emails before I responded to > this. In the lastest version it is two hooks. inode_notifysecctx and > inode_setsecctx which set incore and both respectivly. So what is the desired behavior of these two calls in the case where on-disk and inode secctx are in lockstep? Does "notify" imply "set" in this case? What about the case where there is no "disk", as is the case for virtual filesystems? Would "set" imply "notify" in this case? I think that if the answer to these questions is "it will never come up because it's only for NFS" what you have is an NFS specific interface in the LSM. That may be OK, but it ain't pretty. On the other hand, NFS is sufficiently important that a little ugly may be a price worth paying. > Dave > > > On Fri, 2008-03-07 at 11:05 +0100, Christoph Hellwig wrote: > > On Thu, Mar 06, 2008 at 11:47:06AM -0500, Dave Quigley wrote: > > > Will do. I have to release a new patch set with the hook changed to take > > > a bool instead of a flag so you should see this updated sometime later > > > today. > > > > I think it really should be a separate hook for the two different > > use-cases as suggested by Stephen. > > > Casey Schaufler casey@xxxxxxxxxxxxxxxx -- 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
