Anders Blomdell wrote: > The rationale is the race problems I recently found with pam_namspace > (see https://bugzilla.redhat.com/show_bug.cgi?id=755216). The following > small script and it's output shows what pam_namespace essentially does > does, and the problems that might occur; assume that /work is > automounted, then the following really confuses things: I don't have opinions on this. But please CC: me when your proposal is accepted, for TOMOYO checks mount flags but currently assumes --bind and --make-private are not passed at the same time. I'll add (e.g.) --bind/make-private to TOMOYO's mount flags. -- 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
