Re: [apparmor] [PATCH 2/2] Set cache file tstamp to the mtime of most recent policy file tstamps

On Mon, Jun 08, 2015 at 04:07:44PM -0700, John Johansen wrote: > On 06/08/2015 03:27 PM, Steve Beattie wrote: > > On Fri, Jun 05, 2015 at 03:24:23PM -0700, John Johansen wrote: > >> Currently the cache file has its mtime set to its creation time, but this > >> can lead to cache issues when a policy

Re: [apparmor] [PATCH 2/2] Set cache file tstamp to the mtime of most recent policy file tstamps

On 06/08/2015 03:27 PM, Steve Beattie wrote: > On Fri, Jun 05, 2015 at 03:24:23PM -0700, John Johansen wrote: >> Currently the cache file has its mtime set to its creation time, but this >> can lead to cache issues when a policy file is updated separately from >> the cache file so that is possible

Re: [apparmor] [PATCH 2/2] Set cache file tstamp to the mtime of most recent policy file tstamps

On Fri, Jun 05, 2015 at 03:24:23PM -0700, John Johansen wrote: > Currently the cache file has its mtime set to its creation time, but this > can lead to cache issues when a policy file is updated separately from > the cache file so that is possible a policy file is newer than the > what the cache f

Re: [apparmor] [PATCH 2/2] Set cache file tstamp to the mtime of most recent policy file tstamps

Hello, Am Samstag, 6. Juni 2015 schrieb John Johansen: > On 06/06/2015 06:49 AM, Christian Boltz wrote: > > Am Freitag, 5. Juni 2015 schrieb John Johansen: > >> Currently the cache file has its mtime set to its creation time, > >> but > >> this can lead to cache issues when a policy file is update

Re: [apparmor] [PATCH 2/2] Set cache file tstamp to the mtime of most recent policy file tstamps

On 06/06/2015 06:49 AM, Christian Boltz wrote: > Hello, > > Am Freitag, 5. Juni 2015 schrieb John Johansen: >> Currently the cache file has its mtime set to its creation time, but >> this can lead to cache issues when a policy file is updated >> separately from the cache file so that is possible a

Re: [apparmor] [PATCH 2/2] Set cache file tstamp to the mtime of most recent policy file tstamps

Hello, Am Freitag, 5. Juni 2015 schrieb John Johansen: > Currently the cache file has its mtime set to its creation time, but > this can lead to cache issues when a policy file is updated > separately from the cache file so that is possible a policy file is > newer than the what the cache file was

Re: [apparmor] [PATCH 2/2] Set cache file tstamp to the mtime of most recent policy file tstamps

On Fri, Jun 05, 2015 at 03:24:23PM -0700, John Johansen wrote: > Currently the cache file has its mtime set to its creation time, but this > can lead to cache issues when a policy file is updated separately from > the cache file so that is possible a policy file is newer than the > what the cache f

[apparmor] [PATCH 2/2] Set cache file tstamp to the mtime of most recent policy file tstamps

Currently the cache file has its mtime set to its creation time, but this can lead to cache issues when a policy file is updated separately from the cache file so that is possible a policy file is newer than the what the cache file was generated from but still fails the comparison because the gener