From: Nick Piggin <npiggin@suse.de>
To: Matt Mackall <mpm@selenic.com>
Cc: Hugh Dickins <hugh@veritas.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: pgd_none_or_clear_bad strangeness?
Date: Wed, 3 Oct 2007 13:25:27 +0200 [thread overview]
Message-ID: <20071003112527.GA10437@wotan.suse.de> (raw)
In-Reply-To: <20071002222003.GL19691@waste.org>
On Tue, Oct 02, 2007 at 05:20:03PM -0500, Matt Mackall wrote:
> In lib/pagewalk.c, I've been using the various forms of
> {pgd,pud,pmd}_none_or_clear_bad while walking page tables as that
> seemed the canonical way to do things. Lately (eg with -rc7-mm1),
> these have been triggering messages like "bad pgd 0x01e3" and causing
> nasty double faults. It appears this is actually triggered at the pmd
> level (mm/memory.c:116), though it appears to produce the wrong
> message.
>
> Has something changed here? I'm pretty sure this used to work! Is this
> not a kosher thing to do? Does it make any sense I'd repeatedly run
> into a bad pmd in the middle of bash's page table right after boot?
> The simple _none variant seems to work, but I worry that it's papering
> over a real problem.
No, I think that should be the right thing to do for userspace pages.
You're not walking into a hugetlb area or a kernel mapping are you?
(the bad pgd: line could be important... 0x01e3 would be a linear kernel
mapping I think?).
next prev parent reply other threads:[~2007-10-03 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 22:20 pgd_none_or_clear_bad strangeness? Matt Mackall
2007-10-03 11:25 ` Nick Piggin [this message]
2007-10-03 18:18 ` Hugh Dickins
2007-10-03 21:31 ` Matt Mackall
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=20071003112527.GA10437@wotan.suse.de \
--to=npiggin@suse.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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