From: Dave Hansen <dave@sr71.net> To: linux-kernel@vger.kernel.org Cc: x86@kernel.org, linux-api@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, Dave Hansen <dave@sr71.net>, dave.hansen@linux.intel.com, arnd@arndb.de Subject: [PATCH 7/9] generic syscalls: wire up memory protection keys syscalls Date: Tue, 07 Jun 2016 13:47:25 -0700 [thread overview] Message-ID: <20160607204725.A731CB1E@viggo.jf.intel.com> (raw) In-Reply-To: <20160607204712.594DE00A@viggo.jf.intel.com> From: Dave Hansen <dave.hansen@linux.intel.com> These new syscalls are implemented as generic code, so enable them for architectures like arm64 which use the generic syscall table. According to Arnd: Even if the support is x86 specific for the forseeable future, it may be good to reserve the number just in case. The other architecture specific syscall lists are usually left to the individual arch maintainers, most a lot of the newer architectures share this table. Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> Cc: Arnd Bergmann <arnd@arndb.de> --- b/include/uapi/asm-generic/unistd.h | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff -puN include/uapi/asm-generic/unistd.h~pkeys-119-syscalls-generic include/uapi/asm-generic/unistd.h --- a/include/uapi/asm-generic/unistd.h~pkeys-119-syscalls-generic 2016-06-07 13:22:21.703083776 -0700 +++ b/include/uapi/asm-generic/unistd.h 2016-06-07 13:22:21.707083961 -0700 @@ -724,9 +724,19 @@ __SYSCALL(__NR_copy_file_range, sys_copy __SC_COMP(__NR_preadv2, sys_preadv2, compat_sys_preadv2) #define __NR_pwritev2 287 __SC_COMP(__NR_pwritev2, sys_pwritev2, compat_sys_pwritev2) +#define __NR_pkey_mprotect 288 +__SYSCALL(__NR_pkey_mprotect, sys_pkey_mprotect) +#define __NR_pkey_alloc 289 +__SYSCALL(__NR_pkey_alloc, sys_pkey_alloc) +#define __NR_pkey_free 290 +__SYSCALL(__NR_pkey_free, sys_pkey_free) +#define __NR_pkey_get 291 +__SYSCALL(__NR_pkey_get, sys_pkey_get) +#define __NR_pkey_set 292 +__SYSCALL(__NR_pkey_set, sys_pkey_set) #undef __NR_syscalls -#define __NR_syscalls 288 +#define __NR_syscalls 293 /* * All syscalls below here should go away really, _
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@sr71.net> To: linux-kernel@vger.kernel.org Cc: x86@kernel.org, linux-api@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, Dave Hansen <dave@sr71.net>, dave.hansen@linux.intel.com, arnd@arndb.de Subject: [PATCH 7/9] generic syscalls: wire up memory protection keys syscalls Date: Tue, 07 Jun 2016 13:47:25 -0700 [thread overview] Message-ID: <20160607204725.A731CB1E@viggo.jf.intel.com> (raw) In-Reply-To: <20160607204712.594DE00A@viggo.jf.intel.com> From: Dave Hansen <dave.hansen@linux.intel.com> These new syscalls are implemented as generic code, so enable them for architectures like arm64 which use the generic syscall table. According to Arnd: Even if the support is x86 specific for the forseeable future, it may be good to reserve the number just in case. The other architecture specific syscall lists are usually left to the individual arch maintainers, most a lot of the newer architectures share this table. Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> Cc: Arnd Bergmann <arnd@arndb.de> --- b/include/uapi/asm-generic/unistd.h | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff -puN include/uapi/asm-generic/unistd.h~pkeys-119-syscalls-generic include/uapi/asm-generic/unistd.h --- a/include/uapi/asm-generic/unistd.h~pkeys-119-syscalls-generic 2016-06-07 13:22:21.703083776 -0700 +++ b/include/uapi/asm-generic/unistd.h 2016-06-07 13:22:21.707083961 -0700 @@ -724,9 +724,19 @@ __SYSCALL(__NR_copy_file_range, sys_copy __SC_COMP(__NR_preadv2, sys_preadv2, compat_sys_preadv2) #define __NR_pwritev2 287 __SC_COMP(__NR_pwritev2, sys_pwritev2, compat_sys_pwritev2) +#define __NR_pkey_mprotect 288 +__SYSCALL(__NR_pkey_mprotect, sys_pkey_mprotect) +#define __NR_pkey_alloc 289 +__SYSCALL(__NR_pkey_alloc, sys_pkey_alloc) +#define __NR_pkey_free 290 +__SYSCALL(__NR_pkey_free, sys_pkey_free) +#define __NR_pkey_get 291 +__SYSCALL(__NR_pkey_get, sys_pkey_get) +#define __NR_pkey_set 292 +__SYSCALL(__NR_pkey_set, sys_pkey_set) #undef __NR_syscalls -#define __NR_syscalls 288 +#define __NR_syscalls 293 /* * All syscalls below here should go away really, _ -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-06-07 20:48 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-07 20:47 [PATCH 0/9] [v2] System Calls for Memory Protection Keys Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` [PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` [PATCH 2/9] mm: implement new pkey_mprotect() system call Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` [PATCH 3/9] x86, pkeys: make mprotect_key() mask off additional vm_flags Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` [PATCH 4/9] x86: wire up mprotect_key() system call Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` [PATCH 5/9] x86, pkeys: allocation/free syscalls Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` [PATCH 6/9] x86, pkeys: add pkey set/get syscalls Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` Dave Hansen [this message] 2016-06-07 20:47 ` [PATCH 7/9] generic syscalls: wire up memory protection keys syscalls Dave Hansen 2016-06-07 21:25 ` Arnd Bergmann 2016-06-07 21:25 ` Arnd Bergmann 2016-06-07 20:47 ` [PATCH 8/9] pkeys: add details of system call use to Documentation/ Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-07 20:47 ` [PATCH 9/9] x86, pkeys: add self-tests Dave Hansen 2016-06-07 20:47 ` Dave Hansen 2016-06-08 9:23 ` [PATCH 0/9] [v2] System Calls for Memory Protection Keys Michael Kerrisk (man-pages) 2016-06-08 9:23 ` Michael Kerrisk (man-pages) 2016-06-08 17:35 ` Dave Hansen 2016-06-08 17:35 ` Dave Hansen 2016-06-09 0:01 [PATCH 0/9] [v3] " Dave Hansen 2016-06-09 0:01 ` [PATCH 7/9] generic syscalls: wire up memory protection keys syscalls Dave Hansen 2016-06-09 0:01 ` Dave Hansen 2016-07-07 12:47 [PATCH 0/9] [REVIEW-REQUEST] [v4] System Calls for Memory Protection Keys Dave Hansen 2016-07-07 12:47 ` [PATCH 7/9] generic syscalls: wire up memory protection keys syscalls Dave Hansen 2016-07-07 12:47 ` 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=20160607204725.A731CB1E@viggo.jf.intel.com \ --to=dave@sr71.net \ --cc=akpm@linux-foundation.org \ --cc=arnd@arndb.de \ --cc=dave.hansen@linux.intel.com \ --cc=linux-api@vger.kernel.org \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=torvalds@linux-foundation.org \ --cc=x86@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: linkBe 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.