| commit | 2884f110d5409714f3a04eeb6d2ecd77da66b242 | |
| author | Hugh Dickins <hugh@veritas.com> | |
| Wed, 28 May 2008 18:36:07 +0000 (28 19:36 +0100) | ||
| committer | Thomas Gleixner <tglx@linutronix.de> | |
| Wed, 4 Jun 2008 11:11:47 +0000 (4 13:11 +0200) | ||
| tree | 667c911e164c0e528dc12edd9499224dffd9e1b7 | treesnapshot (tar.gz zip) |
| parent | 226e9a93a253b7d8811b5ed9ac671c6c5a728022 | commitdiff |
x86: fix bad pmd ffff810000207xxx(9090909090909090)
OGAWA Hirofumi and Fede have reported rare pmd_ERROR messages:
mm/memory.c:127: bad pmd ffff810000207xxx(9090909090909090).
Initialization's cleanup_highmap was leaving alignment filler
behind in the pmd for MODULES_VADDR: when vmalloc's guard page
would occupy a new page table, it's not allocated, and then
module unload's vfree hits the bad 9090 pmd entry left over.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
OGAWA Hirofumi and Fede have reported rare pmd_ERROR messages:
mm/memory.c:127: bad pmd ffff810000207xxx(9090909090909090).
Initialization's cleanup_highmap was leaving alignment filler
behind in the pmd for MODULES_VADDR: when vmalloc's guard page
would occupy a new page table, it's not allocated, and then
module unload's vfree hits the bad 9090 pmd entry left over.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
| arch/x86/mm/init_64.c | diffblobblamehistory |