Stephen Smalley <sds@xxxxxxxxxxxxx> wrote: > > + /* We need to check that the union file is allowed to be opened as well > > + * as checking that the lower file is allowed to be opened. > > Hmm...so if I try to open a file for write access, then we are going to > require that the process be allowed to write to both the union/overlay > inode and to the lower inode? That seems problematic for the containers > use case where no write access will be granted to the lower files. Actually, this comment should probably be deleted. I am currently thinking that access through the overlay fs should only be mediated by the label on the overlay inode and should not involve the lower inode. Possibly, then the lower file label should be reckoned against the label of whoever created the *mount*. 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
