From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Implement copy_to_user_page() for noMMU
Date: Tue, 30 Mar 2010 08:29:19 +0100 [thread overview]
Message-ID: <20100330072919.GA14500@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100330013132.GA15598@shareable.org>
On Tue, Mar 30, 2010 at 02:31:32AM +0100, Jamie Lokier wrote:
> Other variations such as writing when a mapping is !VM_EXEC and later
> mapping or mprotecting the same shmem VM_EXEC, but it's even more
> forbidden semantically to write to a read-only mapping (and just as
> unchecked on nommu), and conversion of writable to VM_EXEC ought to
> flush i-cache at mprotect time.
If NX isn't implemented, then arm_elf_read_implies_exec() must return 1
for the CPU - so that any region that is marked readable will have
VM_EXEC set.
next prev parent reply other threads:[~2010-03-30 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 13:24 [PATCH] ARM: Implement copy_to_user_page() for noMMU Catalin Marinas
2010-03-30 1:31 ` Jamie Lokier
2010-03-30 7:29 ` Russell King - ARM Linux [this message]
2010-03-30 9:31 ` Catalin Marinas
2010-03-30 11:33 ` Jamie Lokier
2010-03-30 9:30 ` Catalin Marinas
2010-03-30 11:25 ` Jamie Lokier
2010-03-30 11:50 ` Catalin Marinas
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=20100330072919.GA14500@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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