From: Segher Boessenkool <segher@kernel.crashing.org>
To: linuxppc-dev@ozlabs.org
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: [PATCH] Treat ISI faults as read faults on classic 32-bit PowerPC
Date: Wed, 18 Jul 2007 17:30:19 +0200 [thread overview]
Message-ID: <11847726193856-git-send-email-segher@kernel.crashing.org> (raw)
Message-ID: <5d56173bee3f9ea0050aa508e7f27cc932af7229.1184104284.git.segher@kernel.crashing.org> (raw)
Some old software on ppc32 executes from pages it hasn't marked
executable. Since "classic" hardware doesn't distinguish between
execute and read accesses, the do_page_fault() code shouldn't
either. This makes glibc-2.2 work again on such hardware.
Signed-off-by: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>
Cc: Johannes Berg <johannes@sipsolutions.net>
---
[Resend again, ozlabs' greylisting doesn't like me at all.]
Tested by Scott on 32-bit, glibc-2.2.5 and glibc-2.3.3 (no new
failures and problem solved), and by Johannes on his glibc-2.4
"---p" testcase. Could use testing on ppc64 and BookE too, for
good measure.
This reverts the previous change and makes the bugfix behave
more like the arch/ppc code.
arch/powerpc/mm/fault.c | 14 ++++++++++----
1 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/mm/fault.c b/arch/powerpc/mm/fault.c
index 115b25f..5d7add0 100644
--- a/arch/powerpc/mm/fault.c
+++ b/arch/powerpc/mm/fault.c
@@ -278,14 +278,17 @@ good_area:
goto bad_area;
#endif /* CONFIG_8xx */
+#ifdef CONFIG_PPC64
if (is_exec) {
-#if !(defined(CONFIG_4xx) || defined(CONFIG_BOOKE))
/* protection fault */
if (error_code & DSISR_PROTFAULT)
goto bad_area;
if (!(vma->vm_flags & VM_EXEC))
goto bad_area;
-#else
+ } else
+ /* A read or write, code continues below... */
+#elsif defined(CONFIG_4xx) || defined(CONFIG_BOOKE)
+ if (is_exec) {
pte_t *ptep;
pmd_t *pmdp;
@@ -310,9 +313,12 @@ good_area:
}
pte_unmap_unlock(ptep, ptl);
}
+ } else
+ /* A read or write, code continues below... */
#endif
- /* a write */
- } else if (is_write) {
+
+ /* A read or write. Classic PPC32 execute is considered a read. */
+ if (is_write) {
if (!(vma->vm_flags & VM_WRITE))
goto bad_area;
/* a read */
--
1.5.2.1.144.gabc40-dirty
next prev reply other threads:[~2007-07-18 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d56173bee3f9ea0050aa508e7f27cc932af7229.1184104284.git.segher@kernel.crashing.org>
2007-07-12 9:47 ` [PATCH] Treat ISI faults as read faults on classic 32-bit PowerPC Johannes Berg
2007-07-18 15:30 ` Segher Boessenkool [this message]
2007-07-19 0:00 ` Paul Mackerras
2007-07-19 16:44 ` Jon Loeliger
2007-07-19 17:16 ` Segher Boessenkool
2007-07-19 18:57 ` Jon Loeliger
2007-07-19 19:02 ` Scott Wood
2007-07-19 19:10 ` Jon Loeliger
2007-07-19 20:59 ` Kumar Gala
2007-07-19 18:46 ` Segher Boessenkool
2007-07-19 23:40 ` Paul Mackerras
2007-07-20 7:42 ` Segher Boessenkool
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=11847726193856-git-send-email-segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
/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).