From: "Kip Walker" <kwalker@broadcom.com>
To: linux-mips@oss.sgi.com
Subject: HIGHMEM bug
Date: Wed, 13 Mar 2002 21:28:37 -0800 [thread overview]
Message-ID: <3C903505.36BE8BCC@broadcom.com> (raw)
After several days of hunting, I found a bug in the MIPS highmem code.
A comparison of arch/mips/mm/init.c to arch/i386/mm/init.c supports my
claim.
The PGD entry for the fixed mapping virtual addresses is never
allocated. So what happens is that the fixed mapping pte's get stuffed
into the invalid_pte_table! Then, subsequent accesses that ought to
fault might alias into these PTE's and get satisfied with somebody
else's physical page.
The following patch seems to help a great deal:
Index: arch/mips/mm/init.c
===================================================================
RCS file: /cvs/linux/arch/mips/mm/init.c,v
retrieving revision 1.38.2.4
diff -u -r1.38.2.4 init.c
--- arch/mips/mm/init.c 2002/02/06 18:29:15 1.38.2.4
+++ arch/mips/mm/init.c 2002/03/14 05:25:12
@@ -206,6 +206,12 @@
#ifdef CONFIG_HIGHMEM
/*
+ * Fixed mappings:
+ */
+ vaddr = __fix_to_virt(__end_of_fixed_addresses - 1) & PMD_MASK;
+ fixrange_init(vaddr, 0, pgd_base);
+
+ /*
* Permanent kmaps:
*/
vaddr = PKMAP_BASE;
reply other threads:[~2002-03-14 5:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C903505.36BE8BCC@broadcom.com \
--to=kwalker@broadcom.com \
--cc=linux-mips@oss.sgi.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