[GIT PULL] kmemcheck updates for -tip
From: Vegard Nossum
Date: Thu Feb 26 2009 - 09:02:12 EST
Hi,
The following changes since commit 8f5bd505f147bcd57c627e8599cbcc6b082312d4:
Ingo Molnar (1):
Merge branch 'for-tip' of git://git.kernel.org/.../vegard/kmemcheck into kmemcheck
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vegard/kmemcheck.git for-tip
Pekka Enberg (7):
kmemcheck: Disable SLUB and SLAB debugging when kmemcheck is enabled
kmemcheck: remove forward declarations from error.c
kmemcheck: make initialization message less confusing
kmemcheck: remove multiple ifdef'd definitions of the same global variable
kmemcheck: move 64-bit ifdef out of kmemcheck_opcode_decode()
kmemcheck: missing whitespace in do_page_fault()
kmemcheck: use kmemcheck_pte_lookup() instead of open-coding it
Vegard Nossum (9):
kmemcheck: fix an incorrect BUG_ON()
kmemcheck: fix shadow updates that cross page boundaries
crypto: don't track xor test pages with kmemcheck
x86: don't use MMX/SSE in xor routines if kmemcheck is compiled in
kmemcheck: reverse dependencies between DEBUG_PAGEALLOC and KMEMCHECK
kmemcheck: depend on DEBUG_KERNEL
c2port: annotate bitfield for kmemcheck
kmemcheck (bitfields): don't actually initialize the bitfield
net: annotate struct sock bitfield
arch/x86/Kconfig.debug | 6 +-
arch/x86/include/asm/xor.h | 5 ++
arch/x86/mm/fault.c | 2 +-
arch/x86/mm/kmemcheck/error.c | 137 ++++++++++++++++++-------------------
arch/x86/mm/kmemcheck/kmemcheck.c | 20 ++---
arch/x86/mm/kmemcheck/opcode.c | 9 ++-
arch/x86/mm/kmemcheck/shadow.c | 38 +++++++++-
crypto/xor.c | 7 ++-
drivers/misc/c2port/core.c | 2 +
include/linux/c2port.h | 7 ++-
include/linux/kmemcheck.h | 6 +-
include/net/sock.h | 8 ++-
lib/Kconfig.debug | 4 +-
net/core/sock.c | 2 +
14 files changed, 151 insertions(+), 102 deletions(-)
Vegard
--
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/