Comment 16 for bug 1658219

I encountered this issue on xenial after updating to Azure's 4.15 kernel for testing. We started encountering an apparmor deny which doesn't happen on the latest 4.4 kernel. I had missed setting the k flag for a policy, and everything worked on the new kerenl once we fixed the policy.

Given that this bug leads to incorrect enforcement of policy does it make sense to release a fix for xenial?