out of free space on /tmp causes apparmor loosing protection on reload

[Arkadiusz Miśkiewicz]

If there is no free space on tmp partition then reloading apparmor (init.d/apparmor reload) causes protection/profiles to be lost.

[Simon Déziel (sdeziel)]

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

[Kees Cook (kees)]

If we switch from dash to bash, we can use local fd redirection to avoid the need for /tmp at all.

[Arkadiusz Miśkiewicz (arekm)]

Using bash sucks. We want code that supports POSIX shell.

Also proposed patch is for some code that's not even in apparmor bzr repo .

[Steve Beattie (sbeattie)]

An awk-based fix was committed to both trunk for 2.7 (rev 1805) and to the 2.6 branch (rev 1706).

[Jamie Strandboge (jdstrand)]

This was fixed long ago in Ubuntu.