[ 0/8] 3.4.32-stable review
From: Greg Kroah-Hartman
Date: Fri Feb 15 2013 - 18:01:35 EST
This is the start of the stable review cycle for the 3.4.32 release.
There are 8 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Feb 17 22:53:47 UTC 2013.
Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.4.32-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Linux 3.4.32-rc1
Alexander Duyck <alexander.h.duyck@xxxxxxxxx>
igb: Remove artificial restriction on RQDPC stat reading
Satoru Takeuchi <takeuchi_satoru@xxxxxxxxxxxxxx>
efi: Clear EFI_RUNTIME_SERVICES rather than EFI_BOOT by "noefi" boot parameter
Rafael J. Wysocki <rjw@xxxxxxx>
PCI/PM: Clean up PME state when removing a device
Jan Beulich <JBeulich@xxxxxxxx>
x86/xen: don't assume %ds is usable in xen_iret for 32-bit PVOPS.
Mel Gorman <mgorman@xxxxxxx>
x86/mm: Check if PUD is large when validating a kernel address
Stoney Wang <song-bo.wang@xxxxxx>
x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems
Kees Cook <keescook@xxxxxxxxxxxx>
x86: Do not leak kernel page mapping locations
Heiko Carstens <heiko.carstens@xxxxxxxxxx>
s390/timer: avoid overflow when programming clock comparator
-------------
Diffstat:
Makefile | 4 ++--
arch/s390/kernel/time.c | 3 +++
arch/x86/include/asm/pgtable.h | 5 +++++
arch/x86/kernel/apic/x2apic_phys.c | 21 +++++++++++----------
arch/x86/mm/fault.c | 8 +++++---
arch/x86/mm/init_64.c | 3 +++
arch/x86/platform/efi/efi.c | 2 +-
arch/x86/xen/xen-asm_32.S | 14 +++++++-------
drivers/net/ethernet/intel/igb/igb_main.c | 8 +++++---
drivers/pci/remove.c | 2 ++
10 files changed, 44 insertions(+), 26 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/