apparmor3 backport kernels

[Tim Gardner]

On 06/25/2013 07:00 AM, John Johansen wrote:
> Sorry these have taken longer than I expected I was chasing down a couple
> bugs that popped up in the backport kernels that where show stoppers.
> 
> 
> Just some more details on the backport kernels, so if needed some one else
> can look at and understand what I have done.
> 
> The patches are isolated to the apparmor directory except for the config patch
> I have collapsed it to a single patch to make it easy to revert/sync in new
> versions.
> 
> The original patchsets are on separate branches
> v3.4-backport-of-v3.10-apparmor
> v3.4-backport-of-apparmor3
> 
> v3.1-backport-of-v3.10-apparmor
> v3.1-backport-of-apparmor3
> 
> v3.0-backport-of-v3.10-apparmor
> v3.0-backport-of-apparmor3
> 
> the v3.10-apparmor branches are backports of the current upstream apparmor as
> a base for apparmor3 as that is what it is being dev'd on.
> 
> the apparmor3 branches have a snapshot of the apparmor3 dev tree dropped into
> them. They snapshot has been squashed so its a single patch.
> 
> grouper-presquash-apparmor3
> manguro-presquash-apparmor3
> 
> have the modification to their respective -apparmor3 branches (mostly just
> dropping the backport shim for __d_path changes as these kernels have
> the upstream __d_path patch). These branches where then squashed to arrive
> at the final branch
> 
> 
> the version backport info in the patch description indicates the first
> kernel that needs the patch. So
> UBUNTU: SAUCE: apparmor: 3.6 backport ...
> indicates its a patch dealing with something done in the 3.7 kernel and
> was backported to 3.6.
> 
> 
> All of these branches have been built. The phablet kernels have not been
> tested yet. And I only have the nexus-7 to test on. I will try to un foobar
> my nexus7 today to do testing of the grouper kernel.
> 
> 

Andy and I are working on it...

Cc'd kteam list
-- 
Tim Gardner tim.gardner at canonical.com