From: labbott@fedoraproject.org (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Support for set_memory_* outside of module space
Date: Tue, 3 Nov 2015 13:48:33 -0800 [thread overview]
Message-ID: <1446587315-18145-1-git-send-email-labbott@fedoraproject.org> (raw)
Hi,
Based on a recent discussion[1] there is interest in having set_memory_* work
on kernel memory for security and other use cases. This patch adds the
ability for that to happen behind a kernel option. If this is welcome enough,
the Kconfig can be dropped. This has been briefly tested but not stress tested.
Thanks,
Laura
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/382079.html
Laura Abbott (2):
arm64: Get existing page protections in split_pmd
arm64: Allow changing of attributes outside of modules
arch/arm64/Kconfig.debug | 11 +++++++
arch/arm64/mm/mm.h | 3 ++
arch/arm64/mm/mmu.c | 11 ++++---
arch/arm64/mm/pageattr.c | 74 ++++++++++++++++++++++++++++++++++++++++++++----
4 files changed, 88 insertions(+), 11 deletions(-)
--
2.4.3
next reply other threads:[~2015-11-03 21:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 21:48 Laura Abbott [this message]
2015-11-03 21:48 ` [PATCH 1/2] arm64: Get existing page protections in split_pmd Laura Abbott
2015-11-05 7:07 ` Ard Biesheuvel
2015-11-05 10:15 ` Xishi Qiu
2015-11-06 1:24 ` Laura Abbott
2015-11-03 21:48 ` [PATCH 2/2] arm64: Allow changing of attributes outside of modules Laura Abbott
2015-11-04 3:17 ` zhong jiang
2015-11-05 7:44 ` Ard Biesheuvel
2015-11-06 1:35 ` Laura Abbott
[not found] ` <563974A8.3060306@huawei.com>
[not found] ` <563A4A74.60900@redhat.com>
2015-11-05 11:10 ` Xishi Qiu
2015-11-06 1:11 ` Laura Abbott
2015-11-05 11:29 ` Xishi Qiu
2015-11-03 23:42 ` [PATCH 0/2] Support for set_memory_* outside of module space Kees Cook
2015-11-04 18:51 ` Laura Abbott
2015-11-04 19:06 ` Kees Cook
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=1446587315-18145-1-git-send-email-labbott@fedoraproject.org \
--to=labbott@fedoraproject.org \
--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;
as well as URLs for NNTP newsgroup(s).