summaryrefslogtreecommitdiffstats
path: root/mm/percpu.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2013-02-18 09:58:02 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2013-02-18 09:58:02 -0800
commit7c45512df987c5619db041b5c9b80d281e26d3db (patch)
tree8687da177b111914b165bb723cea20e299731191 /mm/percpu.c
parentf741656d646f7a5b56ba86765205b954237e7956 (diff)
downloadlinux-7c45512df987c5619db041b5c9b80d281e26d3db.tar.gz
linux-7c45512df987c5619db041b5c9b80d281e26d3db.tar.bz2
linux-7c45512df987c5619db041b5c9b80d281e26d3db.zip
mm: fix pageblock bitmap allocation
Commit c060f943d092 ("mm: use aligned zone start for pfn_to_bitidx calculation") fixed out calculation of the index into the pageblock bitmap when a !SPARSEMEM zome was not aligned to pageblock_nr_pages. However, the _allocation_ of that bitmap had never taken this alignment requirement into accout, so depending on the exact size and alignment of the zone, the use of that index could then access past the allocation, resulting in some very subtle memory corruption. This was reported (and bisected) by Ingo Molnar: one of his random config builds would hang with certain very specific kernel command line options. In the meantime, commit c060f943d092 has been marked for stable, so this fix needs to be back-ported to the stable kernels that backported the commit to use the right alignment. Bisected-and-tested-by: Ingo Molnar <mingo@kernel.org> Acked-by: Mel Gorman <mgorman@suse.de> Cc: stable@kernel.org Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/percpu.c')
0 files changed, 0 insertions, 0 deletions