On Fri, Feb 21, 2014 at 10:57:30AM +0800, Qiang Huang wrote: > Hi Greg, > > We've started to analyze the list of upstream commits that have been > backported to 3.2 but missing from 3.4. > > For the 12 commits that I've analyzed, > - 1 commit was reverted in 3.2 stable, and we have the same reason to > skip that in 3.4. > - 1 commit(39d18dc4b8b0 in 3.2) was reverted in 3.2 because the bug would > only affect 3.4+, so we need it in 3.4, with some adjustments. > - 1 commit(1bdb24f5ab52 in 3.2) without stable tag, but it fix CVE-2012-5517, > and can be applied cleanly to 3.4. > - 2 commits were marked for stable but can't be applied cleanly to 3.4. > - 5 commits were marked for stable and can be applied cleanly and the > fix is obviously correct. > > Please cherry-pick those commits from 3.2.x: > > 511c73bcf8e7 s390/kvm: dont announce RRBM support > 1a14c25a0b52 KVM: PPC: Emulate dcbf > da4eda14795e KVM: IOMMU: hva align mapping page size > 7c4bf08d3fa2 proc connector: reject unprivileged listener bumps > 2235df8b82f6 cgroup: fix RCU accesses to task->cgroups > 1bdb24f5ab52 mm/hotplug: correctly add new zone to all other nodes' zone lists Now all queued up. > There are 3 other commits that need trivial context adjustments. I'll > send out the backports. I've applied these as well, thanks so much for doing this work, it's much appreciated. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html