From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org,
David Daney <ddaney@caviumnetworks.com>,
Markos Chandras <Markos.Chandras@imgtec.com>,
James Hogan <james.hogan@imgtec.com>
Subject: [PATCH 0/2] RIXI fixes.
Date: Thu, 23 Jul 2015 11:34:22 +0200 [thread overview]
Message-ID: <cover.1437644062.git.ralf@linux-mips.org> (raw)
As part of unrelated work I ran into issus with RIXI support which allows
the creation of pages that are executable but not readable. Problems
arise with instruction emulation on such pages, for example when a load
or store instruction is taking an unaligned exception, is an FPU
instruction that requires emulation, a trap or break instruction of
which the break code needs to bread and more.
A better solution would be to create a temporary mapping using
kmap_coherent() but that's more complex so left for a later stage.
These patches have been sitting in a shady git tree for years but seem to
work for me. Nevertheless Comments appreciated.
Cheers,
Ralf
Ralf Baechle (2):
MIPS: Handle page faults of executable but unreadable pages correctly.
MIPS: Partially disable RIXI support.
arch/mips/mm/cache.c | 8 ++++----
arch/mips/mm/fault.c | 3 ++-
2 files changed, 6 insertions(+), 5 deletions(-)
--
2.4.3
next reply other threads:[~2015-07-23 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 9:34 Ralf Baechle [this message]
2015-07-23 9:10 ` [PATCH 1/2] MIPS: Handle page faults of executable but unreadable pages correctly Ralf Baechle
2015-07-23 10:15 ` James Hogan
2015-07-23 10:15 ` James Hogan
2015-07-23 12:35 ` Ralf Baechle
2015-07-23 9:10 ` [PATCH 2/2] MIPS: Partially disable RIXI support Ralf Baechle
2015-07-23 10:06 ` James Hogan
2015-07-23 10:06 ` James Hogan
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=cover.1437644062.git.ralf@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Markos.Chandras@imgtec.com \
--cc=ddaney@caviumnetworks.com \
--cc=james.hogan@imgtec.com \
--cc=linux-mips@linux-mips.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