diff options
| author | Hugh Dickins <hugh@veritas.com> | 2008-05-28 19:36:07 +0100 |
|---|---|---|
| committer | Thomas Gleixner <tglx@linutronix.de> | 2008-06-04 13:11:47 +0200 |
| commit | 2884f110d5409714f3a04eeb6d2ecd77da66b242 (patch) | |
| tree | 667c911e164c0e528dc12edd9499224dffd9e1b7 /arch/x86/mm | |
| parent | 226e9a93a253b7d8811b5ed9ac671c6c5a728022 (diff) | |
| download | kernel-crypto-2884f110d5409714f3a04eeb6d2ecd77da66b242.tar.gz kernel-crypto-2884f110d5409714f3a04eeb6d2ecd77da66b242.tar.xz kernel-crypto-2884f110d5409714f3a04eeb6d2ecd77da66b242.zip | |
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>
Diffstat (limited to 'arch/x86/mm')
| -rw-r--r-- | arch/x86/mm/init_64.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c index 32ba13b0f81..998a06ea5f7 100644 --- a/arch/x86/mm/init_64.c +++ b/arch/x86/mm/init_64.c @@ -206,7 +206,7 @@ void __init cleanup_highmap(void) pmd_t *last_pmd = pmd + PTRS_PER_PMD; for (; pmd < last_pmd; pmd++, vaddr += PMD_SIZE) { - if (!pmd_present(*pmd)) + if (pmd_none(*pmd)) continue; if (vaddr < (unsigned long) _text || vaddr > end) set_pmd(pmd, __pmd(0)); |