Messages in this thread | | | From | Geert Uytterhoeven <> | Date | Mon, 21 Jan 2019 09:55:48 +0100 | Subject | Re: [PATCH v2 14/29] arch: add pkey and rseq syscall numbers everywhere |
| |
On Fri, Jan 18, 2019 at 5:20 PM Arnd Bergmann <arnd@arndb.de> wrote: > Most architectures define system call numbers for the rseq and pkey system > calls, even when they don't support the features, and perhaps never will. > > Only a few architectures are missing these, so just define them anyway > for consistency. If we decide to add them later to one of these, the > system call numbers won't get out of sync then. > > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> arch/m68k/kernel/syscalls/syscall.tbl | 4 ++++
> --- a/arch/m68k/kernel/syscalls/syscall.tbl > +++ b/arch/m68k/kernel/syscalls/syscall.tbl > @@ -388,6 +388,10 @@ > 378 common pwritev2 sys_pwritev2 > 379 common statx sys_statx > 380 common seccomp sys_seccomp > +381 common pkey_alloc sys_pkey_alloc > +382 common pkey_free sys_pkey_free > +383 common pkey_mprotect sys_pkey_mprotect > +384 common rseq sys_rseq
Note that all architectures that already define pkey syscalls, list pkey_mprotect first.
Regardless, for m68k: Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> # room for arch specific calls > 393 common semget sys_semget > 394 common semctl sys_semctl
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
| |