Policy cache file mtimes are not being set correctly
Bug #1484178 reported by
Tyler Hicks
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppArmor |
Fix Released
|
Critical
|
Tyler Hicks | ||
apparmor (Ubuntu) |
Fix Released
|
Critical
|
Jamie Strandboge |
Bug Description
Oliver Grawert (ogra) reported that Ubuntu Touch image builds were failing due to incorrect timestamps on pre-compiled policy cache files.
Starting in AppArmor 2.10, the policy cache file's mtime was meant to be updated to be equal to the newest mtime detected
on the profile and abstraction files used to generate the policy cache file:
http://
That change was not correct and resulted in the mtime of the policy cache file to either not be updated (equal to the policy cache file creation time) or to be updated to an incorrect time.
Changed in apparmor (Ubuntu): | |
importance: | Undecided → Critical |
status: | New → Confirmed |
Changed in apparmor (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
To post a comment you must log in.
Fixed with r3220