out of free space on /tmp causes apparmor loosing protection on reload
Bug #775785 reported by
Arkadiusz Miśkiewicz
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppArmor |
Fix Released
|
Undecided
|
Unassigned | ||
2.6 |
Fix Committed
|
Medium
|
Unassigned | ||
2.7 |
Fix Released
|
Medium
|
Unassigned | ||
apparmor (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
If there is no free space on tmp partition then reloading apparmor (init.d/apparmor reload) causes protection/profiles to be lost.
visibility: | private → public |
tags: | added: patch |
Changed in apparmor (Ubuntu): | |
importance: | Undecided → Medium |
milestone: | none → precise-updates |
To post a comment you must log in.
I can reproduce this behaviour on a Natty amd64 VM. In fact, when /tmp is 100% full /etc/init. d/apparmor reload|restart will not pick new profiles.
Also, when you free some space in /tmp even reloading/restart Apparmor will not activate new profiles. I had to use apparmor_parser -a -T -W /etc/apparmor. d/usr.bin. firefox to finally have it.
Sometimes, apparmor reload/restart will give this error :
grep: write error: No space left on device