[lucid, maverick] SRU: apparmor_parser triggers a kernel panic

Stefan Bader stefan.bader at canonical.com
Fri Mar 11 07:56:20 UTC 2011


On 03/10/2011 06:39 PM, Tim Gardner wrote:
> On 03/10/2011 04:11 PM, Paolo Pisati wrote:
> SRU Justification:
> 
>      Impact: kernel panic when loading a malformed apparmor profile.
>      Fix: see attached patch.
>      Testcase: /etc/init.d/apparmor restart
> 
> 
> Buglink:
> https://bugs.launchpad.net/ubuntu/+source/linux-mvl-dove/+bug/732700
> 
> This affetcs lucid/master, lucid/mvl-dove and maverick/mvl-dove.
> 
> This fix a regression in the lucid/mvl-dove -proposed kernel.
> 
> bye,
> p
>>

> Acked-by: Tim Gardner <tim.gardner at canonical.com>

> Its worth noting that this regression has never been discovered on Maverick
> 'cause clearly no-one is using mvl-dove on Maverick.

> rtg

Actually it is probably worth mentioning that this is likely not a problem in
Maverick because dml-dove on Maverick is based on Lucid.

Which brings me to one more note: On future SRUs I would not mention the topic
branches at all if the problem is in a master tree. All those will get the fix
anyway when they are rebased. And it can be a pain to think of all of them. For
example Lucid-ec2 will be affected by this bug, too.

For branch specific SRU requests, I would include that in the subject, eg.

[lucid-mvl-dove] SRU: ...

At least to me this helps a lot to know at a glance what the target of a patch
is (which comes handy later when applying).

I have taken the liberty of extending the commit message by a bit more
explanation and applied and pushed it to lucid-master-next.

-Stefan




More information about the kernel-team mailing list