On Mon, 2014-01-13 at 21:46 +0900, Tetsuo Handa wrote: > Miklos Szeredi wrote: > > Please consider for -next (3.14). > > Excuse me, but did you explain to CONFIG_SECURITY_PATH=y users?
No, sorry. > I don't see changes in TOMOYO and AppArmor directories. > TOMOYO might want to use new keyword like "file swapname" > rather than using "file rename" for cross rename operation. Cross rename (A, B) is equivalent to plain rename(A, B) + plain rename (B, A) done as a single atomic operation. If security module allows both then cross rename is allowed. If at least one is denied then the cross rename is denied. This is prepared for in "[PATCH 06/11] security: add flags to rename hooks" and actually done in "[PATCH 07/11] vfs: add cross-rename". Security people are free to implement a explicit security check for cross rename, but I don't think that is in the scope of this patchset. Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
