From: ebiederm@xmission.com (Eric W. Biederman)
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@elte.hu,
ijc@hellion.org.uk
Subject: Re: early fixmap causes kmap breakage
Date: Mon, 29 Dec 2008 22:22:12 -0800 [thread overview]
Message-ID: <m1tz8m41yj.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <20081230040118.GA27679@wotan.suse.de> (Nick Piggin's message of "Tue, 30 Dec 2008 05:01:18 +0100")
Nick Piggin <npiggin@suse.de> writes:
> On Mon, Dec 29, 2008 at 03:17:31PM -0800, Andrew Morton wrote:
>> On Thu, 18 Dec 2008 22:15:43 +0100
>> Nick Piggin <npiggin@suse.de> wrote:
>>
>> > Hi,
>> >
>> > I've debugged a problem where i386+pae systems with more than a few CPUs
>> > blow up at boot in the kmap_atomic code.
>>
>> ping?
>
> No further progress here, I'm waiting on input for how to fix this
> "nicely". Meantime, clearing the early fixmap pte I guess works, but
> you lose a page... is it possible to put it into .initdata or is
> there some issue with that? (I guess on a PAE kernel, 4K isn't a
> big deal).
>
>
>> > The problem is that the kmap_atomic pte pages all need to be contiguous
>> > memory because the pte is calculated via the first kmap pte page + an
>> > offset (so as not to have to walk the page tables every time).
>> >
>> > The fixmap setup code crudely allocates contiguous pte pages, which is fine,
>> > but if it finds an already populated pmd entry, then it will not switch it
>> > to a new, contiguous pte page. So the early fixmap introduces a discontig
>> > page table right in the middle of the kmap atomic fixmaps.
Where is this?
>> > Commenting out the eaarly fixmap setup in head_32.S gets everything working
>> > properly. What would be the best way to fix this? Could we put the early
>> > fixmap page table in initdata, and then have the fixmap setup proper first
>> > clear its corresponding pmd entry?
Why would we want or need to?
>> How come users/testers aren't reporting this?
>
> Because apparently nobody tests 32-bit PAE systems with more than a couple
> of CPUs anymore. This bug comes from HW vendor doing testing of SLES11.
Hmm.
I have taken a quick skim and I am not seeming the part of the code you are
talking about. Is the problem code in mainline?
I'm guessing it has something to do with reserve_top_address() being called
with a bad value in the normal case. But I don't see it being called
at all in the normal case.
Eric
next prev parent reply other threads:[~2008-12-30 6:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 21:15 early fixmap causes kmap breakage Nick Piggin
2008-12-29 23:17 ` Andrew Morton
2008-12-30 4:01 ` Nick Piggin
2008-12-30 6:13 ` Ingo Molnar
2008-12-30 7:54 ` Nick Piggin
2008-12-30 8:14 ` Nick Piggin
2008-12-30 10:28 ` Nick Piggin
2008-12-30 22:41 ` Eric W. Biederman
2008-12-31 1:54 ` Nick Piggin
2008-12-31 9:01 ` Eric W. Biederman
2008-12-31 9:33 ` Nick Piggin
2009-01-09 10:24 ` Ian Campbell
2008-12-30 6:22 ` Eric W. Biederman [this message]
2008-12-30 6:35 ` Nick Piggin
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=m1tz8m41yj.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=ijc@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.