[apparmor] PATCH [0/2] have caching respect include time stamps

John Johansen john.johansen at canonical.com
Tue Sep 14 11:44:59 BST 2010


Currently whether the cache is invalid is determined by the profile file,
and not the abstractions. This means that if an abstraction is updated
and the profile isn't the cache file is not invalidated.

This is a less than pretty caching patch that does cache timestamp
checking after parsing.  During parsing it finds the most recent timestamp
for all files parsed and compares that to the cache file.

This is a little slower than the before parse check, but it is still
fast as the check is done before any of the compilation of policy is
done.

Later if we choose, we can reintroduce early cache checking by providing
a dot file in the cache directory with the names of the files that
lead to the creation of the cache file, and if that isn't there we can
fall back to this.




More information about the AppArmor mailing list