linux: 2.6.35-28.50 -proposed tracker

We tested the proposed kernel and found two issues with it, a failure on kernel-security due to bug 737676 and another on kvm amd64 (http://reports.qa.ubuntu.com/reports/kernel-sru/home/ubuntu/sru-kernel-test/maverick-2.6.35-22.33-server/kvm-amd64/qrt-kernel-aslr.txt) ; full results are available here: https://wiki.ubuntu.com/QATeam/KernelSRU-maverick-2.6.35-28.50

The patch that fixes 737676 is on the kernel team mailing list awaiting a second "ack" (which I just gave it). However, I believe the security scripts have been updated to check for this and those are what are being run. This is not a regression for this issue.

The failures we've encounter with KVM AMD64 ASLR described at my previous comment are random and the Security Team is unable to reproduce it.

We're faced with building new test cases when the kernels haven't been built yet, so in this case, I guessed wrong about which kernel version would fix the issue. This failure for 737676 should not be considered a regression. I will update the kernel version test.

    def test_093_ptrace_restriction_parent_via_thread(self):
        '''ptrace of child works from parent threads (LP: #737676)'''

        if self.lsb_release['Release'] < 10.10:
            self._skipped("only Maverick and later")
        expected = 0
        if self.lsb_release['Release'] == 10.10:
            if testlib.dpkg_compare_versions(self.kernel_version_ubuntu, 'le', '2.6.35-28.49') == 0:
                expected = 2

As for the amd64 heap/stack ASLR collision, what is "2.6.35-22.33-server/amd64"? The expected version (2.6.35-28.50-server/amd64) passes this test (as do 2.6.35-28.50-generic/amd64 2.6.35-28.50-generic/amd64 and 2.6.35-28.50-generic/amd64). Obviously that kernel version shouldn't be the one to be tested, so its failure is irrelevant.

Also why isn't the dbench failures of "2.6.35-28.50-generic/amd64 (KVM)" an issue? Note that http://reports.qa.ubuntu.com/reports/kernel-sru/home/ubuntu/sru-kernel-test/maverick-2.6.35-28.50-generic/kvm-amd64/test-dbench.txt is 404, as well as http://reports.qa.ubuntu.com/reports/kernel-sru/home/ubuntu/sru-kernel-test/maverick-2.6.35-28.50-generic/kvm-amd64/qrt-kernel-security.txt

Hardware Certification have completed testing of 105/1116 systems:

http://people.canonical.com/~hwcert/sru-testing/wk14_2011/maverick-proposed.html

11 systems did not run due to infrastructure issues. No regressions were found.

This bug was fixed in the package linux - 2.6.35-28.50

---------------
linux (2.6.35-28.50) maverick-proposed; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #734399

  [ Corentin Chary ]

  * SAUCE: (drop after 2.6.38) eeepc-wmi: reorder keymap
    - LP: #689393
  * SAUCE: (drop after 2.6.38) eeepc-wmi: add wlan key found on 1015P
    - LP: #689393

  [ Keng-Yu Lin ]

  * SAUCE: eeepc-wmi: set the touchpad toggle key code to F22
    - LP: #689393

  [ Tim Gardner ]

  * [Config] CONFIG_BOOT_PRINTK_DELAY=y
    - LP: #733191

  [ Upstream Kernel Changes ]

  * Revert "drm/radeon/bo: add some fallback placements for VRAM only
    objects."
    - LP: #652934
  * eeepc-wmi: add additional hotkeys
    - LP: #689393
  * xen: don't bother to stop other cpus on shutdown/reboot
    - LP: #727814
  * Yama: use thread group leader when creating match
    - LP: #729839
  * mmc: sdhci-pci: add ricoh e822 pci id with device specific quirks
    - LP: #730820
 -- Brad Figg <email address hidden> Sun, 13 Mar 2011 07:01:39 -0700