Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
From: Pavel Machek
Date: Fri Jun 15 2007 - 20:22:16 EST
> >>Under the restorecon proposal, the web site would be horribly broken
> >>until restorecon finishes, as various random pages are or are not
> >>accessible to Apache.
> >Usually you don't do that by doing a 'mv' otherwise you are almost
> >guaranteed stale and mixed up content for some period of time, not to
> >mention the issues surrounding paths that might be messed up.
> on the contrary, useing 'mv' is by far the cleanest way to do this.
> mv htdocs htdocs.old;mv htdocs.new htdocs
> this makes two atomic changes to the filesystem, but can generate
> thousands to millions of permission changes as a result.
Ok, so mv gets slower for big trees... and open() gets faster for deep
trees. Previously, open in current directory was one atomic read of
directory entry, now it has to read directory, and its parent, and its
parent parent, and its...
(Or am I wrong and getting full path does not need to bring anything
in, not even in cache-cold case?)
So, proposed solution has different performance tradeoffs, but should
still be a win -- opens are more common than moves.
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/