--- David Howells <[EMAIL PROTECTED]> wrote: > Stephen Smalley <[EMAIL PROTECTED]> wrote: > > > The cache files are created by the cachefiles kernel module, not by the > > userspace daemon, and the userspace daemon doesn't need to directly > > read/write them at all > > That is correct. > > > (but I think it does need to be able to unlink them?). > > Indeed. > > > The userspace daemon merely identifies the directory where the cache should > > live as part of configuring the cache when enabling it. > > That is the way it currently works, yes. > > > Hence, it is fine to use a fixed label for the cache files (systemhigh > > in a MLS world), and to let the directory's label serve as the basis for > > it. > > That is what I currently do. SELinux rules are provided to grant the > appropriate file accesses to the override label used by the kernel module, so > that it can't go and stamp on files with the wrong label. > > > Only the cachefiles kernel module directly reads and writes the files. > > Correct.
Well, my bad, and thank you for clearing up my misunderstanding. Casey Schaufler [EMAIL PROTECTED] -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
