[apparmor] AppArmor continuing to confine process after calling rcapparmor stop

[John Johansen]

On 07/11/2014 10:36 AM, Miklos Szeredi wrote:
> I've a bug report saying that a process continues to be confined after
> the profile has been removed.
> 
> As far as my reading of the code goes, this is exactly what should
> happen, since common_perm() will call __aa_current_profile() which
> will use the obsolete profile.   Is this intentional?
> 
No, this needs to be fixed, and has been in later dev trees, but they
won't apply. What kernels versions are we looking at so I can provide
a backport patch.