linux-ec2: 2.6.31-308.29 -proposed tracker

Accepted linux-ec2 into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Do we still actually want to QA this, or shall we just declare it dead and I'll remove it from -proposed?

Yes, we really should release this. The main kernel with the same fixes has already been released, it would be best if the final kernels for Karmic were the same for the main and ec2 kernels.

Stefan is going to test this kernel, then if that succeeds we can publish it and declare Karmic truly dead.

Tests ran successful, so we can publish and order the funeral.

This bug was fixed in the package linux-ec2 - 2.6.31-308.29

---------------
linux-ec2 (2.6.31-308.29) karmic-proposed; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #737761

  [ Brad Figg ]

  * Rebased to 2.6.31-23.75

  [ Ubuntu: 2.6.31-23.75 ]

  * Release Tracking Bug
    - LP: #737663
  * do_exit(): make sure that we run with get_fs() == USER_DS,
    CVE-2010-4258
    - LP: #723945
    - CVE-2010-4258
  * xfs: always use iget in bulkstat
    - LP: #692848
  * x25: Prevent crashing when parsing bad X.25 facilities CVE-2010-4164
    - LP: #731199
    - CVE-2010-4164
  * Revised [CVE-2010-4345 Karmic] install_special_mapping skips
    security_file_mmap check. CVE-2010-4346
    - LP: #731971
    - CVE-2010-4346
  * econet: Fix crash in aun_incoming(). CVE-2010-4342
    - LP: #736394
    - CVE-2010-4342
 -- Brad Figg <email address hidden> Fri, 18 Mar 2011 11:55:37 -0700

QA did not test this kernel. Marking as verification-needed, and waiting for input from stakeholders.

This kernel has not been included in an ec2 image (last one was cut on May 2nd). At this point, the karmic kernels are not matching between the desktop and ec2 images.

Just to clarify:
The final karmic ec2 image was generated using 2.6.31.307.6. With Karmic ec2, it is not possible for the user to update their own kernel within ec2. Therefore, this update does not effect the cloud images. However, it is still avaliable in karmic-updates if someone wanted to roll their own image (i suspect this use case is nil).

Thanks.