From: akpm@linux-foundation.org
To: danielmicay@gmail.com, keescook@chromium.org, mm-commits@vger.kernel.org
Subject: [merged] mark-protection_map-as-__ro_after_init.patch removed from -mm tree
Date: Fri, 07 Jul 2017 12:08:11 -0700 [thread overview]
Message-ID: <20170707190811.THKB2msVF%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm/mmap.c: mark protection_map as __ro_after_init
has been removed from the -mm tree. Its filename was
mark-protection_map-as-__ro_after_init.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Daniel Micay <danielmicay@gmail.com>
Subject: mm/mmap.c: mark protection_map as __ro_after_init
The protection map is only modified by per-arch init code so it can be
protected from writes after the init code runs.
This change was extracted from PaX where it's part of KERNEXEC.
Link: http://lkml.kernel.org/r/20170510174441.26163-1-danielmicay@gmail.com
Signed-off-by: Daniel Micay <danielmicay@gmail.com>
Acked-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/mmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/mmap.c~mark-protection_map-as-__ro_after_init mm/mmap.c
--- a/mm/mmap.c~mark-protection_map-as-__ro_after_init
+++ a/mm/mmap.c
@@ -94,7 +94,7 @@ static void unmap_region(struct mm_struc
* w: (no) no
* x: (yes) yes
*/
-pgprot_t protection_map[16] = {
+pgprot_t protection_map[16] __ro_after_init = {
__P000, __P001, __P010, __P011, __P100, __P101, __P110, __P111,
__S000, __S001, __S010, __S011, __S100, __S101, __S110, __S111
};
_
Patches currently in -mm which might be from danielmicay@gmail.com are
include-linux-stringh-add-the-option-of-fortified-stringh-functions.patch
reply other threads:[~2017-07-07 19:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170707190811.THKB2msVF%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=danielmicay@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.