From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Greg KH <greg@kroah.com>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: Top kernel oopses/warnings for the week of May 30th 2008
Date: Fri, 30 May 2008 15:30:06 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805301517500.3141@woody.linux-foundation.org> (raw)
In-Reply-To: <48407909.5090608@linux.intel.com>
On Fri, 30 May 2008, Arjan van de Ven wrote:
>
> ok for some it did gather this information, and it is
>
> kernel BUG at mm/highmem.c:319!
That's just _odd_. The call chain actually has kmap() in it, and kmap
does:
if (!PageHighMem(page))
return page_address(page);
return kmap_high(page);
so if it's the one at line 319, which says
BUG_ON(!PageHighMem(page));
then I wonder what happened to that PageHighMem() test of the page in
between..
Ahh.. Not the same "page". It looks like it's in the
flush_all_zero_pkmaps() path, and it's clearing some _other_ page in the
pkmap table in order to make room for the new one. So the page that causes
problems is from here:
page = pte_page(pkmap_page_table[i]);
rather than the one we're trying to map.
Not that it explains the BUG_ON(). We should only insert page table
entries into the pkmap_page_table[] array in map_new_virtual(), which in
turn is only called from kmap_high(), which in turn means that *those*
pages have also gine through the PageHighMem() test.
So it sounds like we either
- have corruption in pkmap_page_table[]
- or pte_page() doesn't reverse mk_pte(page) propely, and one or the
other is broken.
Does anybody know if the fc9 x86-32 kernel is built with PAE enabled?
Might this be another PAE bit-masking bug and thus possibly fixed by the
PTE_MASK changes?
Linus
next prev parent reply other threads:[~2008-05-30 22:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 16:39 Arjan van de Ven
2008-05-30 19:19 ` Hugh Dickins
2008-05-30 21:43 ` Linus Torvalds
2008-05-30 21:49 ` Arjan van de Ven
2008-05-30 22:17 ` Arjan van de Ven
2008-05-30 22:00 ` Arjan van de Ven
2008-05-30 22:30 ` Linus Torvalds [this message]
2008-05-30 22:34 ` Arjan van de Ven
2008-05-30 22:55 ` Linus Torvalds
2008-05-31 0:41 ` Dave Jones
2008-06-02 23:44 ` Hugh Dickins
2008-06-03 0:00 ` Andrew Morton
2008-06-03 0:41 ` Hugh Dickins
2008-06-03 1:19 ` Andrew Morton
2008-06-09 16:32 ` Ingo Molnar
2008-06-10 12:42 ` Hugh Dickins
2008-05-30 22:34 ` Jochen Voß
2008-05-30 22:36 ` Arjan van de Ven
2008-06-02 0:02 ` James Morris
2008-06-02 2:27 ` Arjan van de Ven
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=alpine.LFD.1.10.0805301517500.3141@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=greg@kroah.com \
--cc=hugh@veritas.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®