mirror of
https://gitlab.com/apparmor/apparmor
synced 2025-08-31 14:25:52 +00:00
Set cache file tstamp to the mtime of most recent policy file tstamp
Currently the cache file has its mtime set at creation time, but this can lead to cache issues when a policy file is updated separately from the cache. This makes it possible for an update to ship a policy file that is newer than the what the cache file was generated from, but result in a cache hit because the cache file was local compiled after the policy file was package into an update (this requires the update to set the mtime of the file when locally installed to the mtime of the file in its update archive but this is commonly done, especially in image based updates). Signed-off-by: John Johansen <john.johansen@canonical.com> Acked-by: Seth Arnold <seth.arnold@canonical.com>
This commit is contained in:
@@ -333,7 +333,6 @@ extern int abort_on_error;
|
||||
extern int skip_bad_cache_rebuild;
|
||||
extern int mru_skip_cache;
|
||||
extern int debug_cache;
|
||||
extern struct timespec mru_tstamp;
|
||||
|
||||
/* provided by parser_lex.l (cannot be used in tst builds) */
|
||||
extern FILE *yyin;
|
||||
|
Reference in New Issue
Block a user