summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorChristoph Lameter <cl@linux.com>2013-07-02 21:12:10 +0200
committerPekka Enberg <penberg@kernel.org>2013-07-07 17:58:31 +0200
commit0f8f8094d28eb53368ac09186ea6b3a324cc7d44 (patch)
tree4f2d98ae905ce6405291880c034b18c8e59e2839 /include
parentslob: use DIV_ROUND_UP where possible (diff)
downloadlinux-0f8f8094d28eb53368ac09186ea6b3a324cc7d44.tar.xz
linux-0f8f8094d28eb53368ac09186ea6b3a324cc7d44.zip
slab: fix init_lock_keys
Some architectures (e.g. powerpc built with CONFIG_PPC_256K_PAGES=y CONFIG_FORCE_MAX_ZONEORDER=11) get PAGE_SHIFT + MAX_ORDER > 26. In 3.10 kernels, CONFIG_LOCKDEP=y with PAGE_SHIFT + MAX_ORDER > 26 makes init_lock_keys() dereference beyond kmalloc_caches[26]. This leads to an unbootable system (kernel panic at initializing SLAB) if one of kmalloc_caches[26...PAGE_SHIFT+MAX_ORDER-1] is not NULL. Fix this by making sure that init_lock_keys() does not dereference beyond kmalloc_caches[26] arrays. Signed-off-by: Christoph Lameter <cl@linux.com> Reported-by: Tetsuo Handa <penguin-kernel@I-Love.SAKURA.ne.jp> Cc: Pekka Enberg <penberg@kernel.org> Cc: <stable@vger.kernel.org> [3.10.x] Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Pekka Enberg <penberg@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions