From: Dave Hansen <dave-gkUM19QKKo4@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
Dave Hansen <dave-gkUM19QKKo4@public.gmane.org>,
dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
arnd-r2nGTMty4D4@public.gmane.org,
tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] x86/pkeys: fix pkeys build breakage for some non-x86 arches
Date: Mon, 12 Sep 2016 13:38:42 -0700 [thread overview]
Message-ID: <20160912203842.48E7AC50@viggo.jf.intel.com> (raw)
From: Dave Hansen <dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Guenter Roeck reported [1] breakage on the h8300 and c6x
architectures (among others) caused by the new memory protection
keys syscalls. This patch does what Arnd suggested and adds them
to kernel/sys_ni.c.
1. http://marc.info/?l=linux-kernel&m=147369214820072&w=2
Signed-off-by: Dave Hansen <dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Tested-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Acked-by: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Cc: "open list:ABI/API" <linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
---
b/kernel/sys_ni.c | 5 +++++
1 file changed, 5 insertions(+)
diff -puN kernel/sys_ni.c~fix-pkeys-arch-breakage kernel/sys_ni.c
--- a/kernel/sys_ni.c~fix-pkeys-arch-breakage 2016-09-12 13:35:17.449066541 -0700
+++ b/kernel/sys_ni.c 2016-09-12 13:35:17.452066676 -0700
@@ -250,3 +250,8 @@ cond_syscall(sys_execveat);
/* membarrier */
cond_syscall(sys_membarrier);
+
+/* memory protection keys */
+cond_syscall(sys_pkey_mprotect);
+cond_syscall(sys_pkey_alloc);
+cond_syscall(sys_pkey_free);
_
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@sr71.net>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, Dave Hansen <dave@sr71.net>,
dave.hansen@intel.com, arnd@arndb.de, tglx@linutronix.de,
linux-api@vger.kernel.org, linux-arch@vger.kernel.org
Subject: [PATCH] x86/pkeys: fix pkeys build breakage for some non-x86 arches
Date: Mon, 12 Sep 2016 13:38:42 -0700 [thread overview]
Message-ID: <20160912203842.48E7AC50@viggo.jf.intel.com> (raw)
Message-ID: <20160912203842.JZEwLTpGeTp9KStrDKavV01aIBwiDRqR6aQV0ZI8wVM@z> (raw)
From: Dave Hansen <dave.hansen@intel.com>
Guenter Roeck reported [1] breakage on the h8300 and c6x
architectures (among others) caused by the new memory protection
keys syscalls. This patch does what Arnd suggested and adds them
to kernel/sys_ni.c.
1. http://marc.info/?l=linux-kernel&m=147369214820072&w=2
Signed-off-by: Dave Hansen <dave.hansen@intel.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "open list:ABI/API" <linux-api@vger.kernel.org>
Cc: linux-arch@vger.kernel.org
---
b/kernel/sys_ni.c | 5 +++++
1 file changed, 5 insertions(+)
diff -puN kernel/sys_ni.c~fix-pkeys-arch-breakage kernel/sys_ni.c
--- a/kernel/sys_ni.c~fix-pkeys-arch-breakage 2016-09-12 13:35:17.449066541 -0700
+++ b/kernel/sys_ni.c 2016-09-12 13:35:17.452066676 -0700
@@ -250,3 +250,8 @@ cond_syscall(sys_execveat);
/* membarrier */
cond_syscall(sys_membarrier);
+
+/* memory protection keys */
+cond_syscall(sys_pkey_mprotect);
+cond_syscall(sys_pkey_alloc);
+cond_syscall(sys_pkey_free);
_
next reply other threads:[~2016-09-12 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 20:38 Dave Hansen [this message]
2016-09-12 20:38 ` [PATCH] x86/pkeys: fix pkeys build breakage for some non-x86 arches Dave Hansen
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=20160912203842.48E7AC50@viggo.jf.intel.com \
--to=dave-gkum19qkko4@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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