From: Laura Abbott <labbott@fedoraproject.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Zhong Jiang <zhongjiang@huawei.com>
Cc: Laura Abbott <labbott@fedoraproject.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Xishi Qiu <qiuxishi@huawei.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: [PATCHv2 0/2] Support for set_memory_* outside of module space
Date: Tue, 10 Nov 2015 17:57:35 -0800 [thread overview]
Message-ID: <1447207057-11323-1-git-send-email-labbott@fedoraproject.org> (raw)
Hi,
This is v2 of the series to allow set_memory_* to work on kernel memory
for security and other use cases. Should have addressed most comments
although another look might be necessary for the contiguous bit.
Thanks,
Laura
Laura Abbott (2):
arm64: Get existing page protections in split_pmd
arm64: Allow changing of attributes outside of modules
arch/arm64/Kconfig | 12 ++++
arch/arm64/mm/mm.h | 3 +
arch/arm64/mm/mmu.c | 12 ++--
arch/arm64/mm/pageattr.c | 174 +++++++++++++++++++++++++++++++++++++++++------
4 files changed, 174 insertions(+), 27 deletions(-)
--
2.5.0
next reply other threads:[~2015-11-11 1:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 1:57 Laura Abbott [this message]
2015-11-11 1:57 ` [PATCHv2 1/2] arm64: Get existing page protections in split_pmd Laura Abbott
2015-11-15 7:32 ` Ard Biesheuvel
2015-11-11 1:57 ` [PATCHv2 2/2] arm64: Allow changing of attributes outside of modules Laura Abbott
2015-11-12 11:55 ` zhong jiang
2015-11-12 16:31 ` Laura Abbott
2015-11-13 2:05 ` zhong jiang
2015-11-13 19:05 ` Laura Abbott
2015-11-13 2:37 ` zhong jiang
2015-11-13 8:27 ` Xishi Qiu
2015-11-13 8:32 ` Xishi Qiu
2015-11-13 19:09 ` Laura Abbott
2015-11-24 23:39 ` [PATCHv2 0/2] Support for set_memory_* outside of module space Laura Abbott
2015-11-25 12:05 ` Will Deacon
2016-01-12 0:47 ` Laura Abbott
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=1447207057-11323-1-git-send-email-labbott@fedoraproject.org \
--to=labbott@fedoraproject.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=qiuxishi@huawei.com \
--cc=will.deacon@arm.com \
--cc=zhongjiang@huawei.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
all inboxes | Powered by JetHome®