Stephen Smalley <sds@xxxxxxxxxxxxx> wrote: > > The third case is the tricky one because we have to try and derive a > > label. I've copied the code from the inode creation - so unless the > > policy changes or the parent directory inode changes, I would've thought > > we'd be okay. > > Only if the filesystem ultimately calls security_inode_init_security() > on the new inode. I'm not sure what you mean? What new inode? The isec label derived by the code goes in the file struct, not the inode struct because we can only get here if there isn't an inode struct. David -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
