From: Ingo Molnar <mingo@elte.hu>
To: Hugh Dickins <hugh@veritas.com>
Cc: Fede <fedux@lugmen.org.ar>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Jan Engelhardt <jengelh@medozas.de>, Willy Tarreau <w@1wt.eu>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] Re: bad pmd ffff810000207238(9090909090909090).
Date: Wed, 28 May 2008 20:40:06 +0200 [thread overview]
Message-ID: <20080528184006.GA14585@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0805281922530.7959@blonde.site>
* Hugh Dickins <hugh@veritas.com> wrote:
> [PATCH] 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.
applied, nice catch!
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-05-28 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <483CBCDD.10401@lugmen.org.ar>
2008-05-28 18:36 ` [PATCH] Re: bad pmd ffff810000207238(9090909090909090) Hugh Dickins
2008-05-28 18:40 ` Ingo Molnar [this message]
2008-05-28 19:56 ` Willy Tarreau
2008-05-28 20:14 ` Jan Engelhardt
2008-05-28 20:43 ` Willy Tarreau
2008-05-28 21:24 ` Jan Engelhardt
2008-05-28 22:20 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080528184006.GA14585@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=fedux@lugmen.org.ar \
--cc=hirofumi@mail.parknet.co.jp \
--cc=hugh@veritas.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).