[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <731438883ae3bcffa05ff014dda773a6c1e3c899.camel@intel.com>
Date: Thu, 14 Sep 2023 22:08:05 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Mehta, Sohil" <sohil.mehta@...el.com>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>
CC: "svens@...ux.ibm.com" <svens@...ux.ibm.com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"schwab@...ux-m68k.org" <schwab@...ux-m68k.org>,
"brgerst@...il.com" <brgerst@...il.com>,
"alexander.shishkin@...ux.intel.com"
<alexander.shishkin@...ux.intel.com>,
"linux-perf-users@...r.kernel.org" <linux-perf-users@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"monstr@...str.eu" <monstr@...str.eu>,
"borntraeger@...ux.ibm.com" <borntraeger@...ux.ibm.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"christophe.leroy@...roup.eu" <christophe.leroy@...roup.eu>,
"mark.rutland@....com" <mark.rutland@....com>,
"glaubitz@...sik.fu-berlin.de" <glaubitz@...sik.fu-berlin.de>,
"dalias@...c.org" <dalias@...c.org>,
"lukas.bulwahn@...il.com" <lukas.bulwahn@...il.com>,
"rdunlap@...radead.org" <rdunlap@...radead.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hca@...ux.ibm.com" <hca@...ux.ibm.com>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
"sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>,
"arnd@...db.de" <arnd@...db.de>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
"ebiederm@...ssion.com" <ebiederm@...ssion.com>,
"Lutomirski, Andy" <luto@...nel.org>,
"jolsa@...nel.org" <jolsa@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-parisc@...r.kernel.org" <linux-parisc@...r.kernel.org>,
"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"mpe@...erman.id.au" <mpe@...erman.id.au>,
"geert@...ux-m68k.org" <geert@...ux-m68k.org>,
"hpa@...or.com" <hpa@...or.com>,
"James.Bottomley@...senPartnership.com"
<James.Bottomley@...senPartnership.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"ink@...assic.park.msu.ru" <ink@...assic.park.msu.ru>,
"linux-m68k@...ts.linux-m68k.org" <linux-m68k@...ts.linux-m68k.org>,
"tsbogend@...ha.franken.de" <tsbogend@...ha.franken.de>,
"broonie@...nel.org" <broonie@...nel.org>,
"Hunter, Adrian" <adrian.hunter@...el.com>,
"acme@...nel.org" <acme@...nel.org>,
"ysato@...rs.sourceforge.jp" <ysato@...rs.sourceforge.jp>,
"deller@....de" <deller@....de>,
"debug@...osinc.com" <debug@...osinc.com>,
"rmclure@...ux.ibm.com" <rmclure@...ux.ibm.com>,
"gor@...ux.ibm.com" <gor@...ux.ibm.com>,
"slyich@...il.com" <slyich@...il.com>,
"npiggin@...il.com" <npiggin@...il.com>,
"agordeev@...ux.ibm.com" <agordeev@...ux.ibm.com>,
"chris@...kel.net" <chris@...kel.net>,
"mingo@...hat.com" <mingo@...hat.com>,
"linux-alpha@...r.kernel.org" <linux-alpha@...r.kernel.org>,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
"mattst88@...il.com" <mattst88@...il.com>,
"linux-s390@...r.kernel.org" <linux-s390@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"jcmvbkbc@...il.com" <jcmvbkbc@...il.com>,
"bp@...en8.de" <bp@...en8.de>,
"richard.henderson@...aro.org" <richard.henderson@...aro.org>,
"irogers@...gle.com" <irogers@...gle.com>,
"namhyung@...nel.org" <namhyung@...nel.org>,
"will@...nel.org" <will@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>
Subject: Re: [PATCH v2] arch: Reserve map_shadow_stack() syscall number for
all architectures
On Thu, 2023-09-14 at 18:58 +0000, Sohil Mehta wrote:
> commit c35559f94ebc ("x86/shstk: Introduce map_shadow_stack syscall")
> recently added support for map_shadow_stack() but it is limited to
> x86
> only for now. There is a possibility that other architectures
> (namely,
> arm64 and RISC-V), that are implementing equivalent support for
> shadow
> stacks, might need to add support for it.
>
> Independent of that, reserving arch-specific syscall numbers in the
> syscall tables of all architectures is good practice and would help
> avoid future conflicts. map_shadow_stack() is marked as a conditional
> syscall in sys_ni.c. Adding it to the syscall tables of other
> architectures is harmless and would return ENOSYS when exercised.
>
> Note, map_shadow_stack() was assigned #453 during the merge process
> since #452 was taken by fchmodat2().
>
> For Powerpc, map it to sys_ni_syscall() as is the norm for Powerpc
> syscall tables.
>
> For Alpha, map_shadow_stack() takes up #563 as Alpha still diverges
> from
> the common syscall numbering system in the other architectures.
Reviewed-by: Rick Edgecombe <rick.p.edgecombe@...el.com>
Powered by blists - more mailing lists