On Thu, Mar 06, 2008 at 08:50:22AM -0500, Stephen Smalley wrote: > In-core only: NFS client gets the file security context for an inode > from the server and needs to set the in-core security context for its > inode accordingly. But it does not want to call back to i_op->setxattr > and try to _set_ the context on the server when it does this. So it > only calls with the incore flag. > > On-disk: NFS server receives a file security context to set on a file > from the client, and wants to update both the in-core security context > for the inode and the on-disk xattr. So it calls with the ondisk flag. > > It actually only requires a boolean flag. Yes, the boolean might be better. I still don't quite understand why we would only set the security context in-core only as this looks like a potential loss of metadata updates for me. -- 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
