[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3bd9a85c6f10279af6372cf17064978ad38c18b3.camel@intel.com>
Date: Fri, 6 Oct 2023 20:01:31 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Mehta, Sohil" <sohil.mehta@...el.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"arnd@...db.de" <arnd@...db.de>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>
CC: "borntraeger@...ux.ibm.com" <borntraeger@...ux.ibm.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"deller@....de" <deller@....de>,
"lukas.bulwahn@...il.com" <lukas.bulwahn@...il.com>,
"irogers@...gle.com" <irogers@...gle.com>,
"agordeev@...ux.ibm.com" <agordeev@...ux.ibm.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"Lutomirski, Andy" <luto@...nel.org>,
"jcmvbkbc@...il.com" <jcmvbkbc@...il.com>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
"ysato@...rs.sourceforge.jp" <ysato@...rs.sourceforge.jp>,
"Hunter, Adrian" <adrian.hunter@...el.com>,
"chris@...kel.net" <chris@...kel.net>,
"hca@...ux.ibm.com" <hca@...ux.ibm.com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"peterz@...radead.org" <peterz@...radead.org>,
"brgerst@...il.com" <brgerst@...il.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"broonie@...nel.org" <broonie@...nel.org>,
"linux-s390@...r.kernel.org" <linux-s390@...r.kernel.org>,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
"christophe.leroy@...roup.eu" <christophe.leroy@...roup.eu>,
"x86@...nel.org" <x86@...nel.org>,
"mpe@...erman.id.au" <mpe@...erman.id.au>,
"tsbogend@...ha.franken.de" <tsbogend@...ha.franken.de>,
"ink@...assic.park.msu.ru" <ink@...assic.park.msu.ru>,
"bp@...en8.de" <bp@...en8.de>,
"geert@...ux-m68k.org" <geert@...ux-m68k.org>,
"rdunlap@...radead.org" <rdunlap@...radead.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
"namhyung@...nel.org" <namhyung@...nel.org>,
"jolsa@...nel.org" <jolsa@...nel.org>,
"npiggin@...il.com" <npiggin@...il.com>,
"monstr@...str.eu" <monstr@...str.eu>,
"linux-m68k@...ts.linux-m68k.org" <linux-m68k@...ts.linux-m68k.org>,
"debug@...osinc.com" <debug@...osinc.com>,
"ebiederm@...ssion.com" <ebiederm@...ssion.com>,
"richard.henderson@...aro.org" <richard.henderson@...aro.org>,
"will@...nel.org" <will@...nel.org>,
"hpa@...or.com" <hpa@...or.com>,
"gor@...ux.ibm.com" <gor@...ux.ibm.com>,
"alexander.shishkin@...ux.intel.com"
<alexander.shishkin@...ux.intel.com>,
"mattst88@...il.com" <mattst88@...il.com>,
"glaubitz@...sik.fu-berlin.de" <glaubitz@...sik.fu-berlin.de>,
"linux-parisc@...r.kernel.org" <linux-parisc@...r.kernel.org>,
"acme@...nel.org" <acme@...nel.org>,
"slyich@...il.com" <slyich@...il.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-alpha@...r.kernel.org" <linux-alpha@...r.kernel.org>,
"James.Bottomley@...senPartnership.com"
<James.Bottomley@...senPartnership.com>,
"rmclure@...ux.ibm.com" <rmclure@...ux.ibm.com>,
"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
"svens@...ux.ibm.com" <svens@...ux.ibm.com>,
"dalias@...c.org" <dalias@...c.org>,
"schwab@...ux-m68k.org" <schwab@...ux-m68k.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>,
"linux-perf-users@...r.kernel.org" <linux-perf-users@...r.kernel.org>
Subject: Re: [PATCH v2] arch: Reserve map_shadow_stack() syscall number for
all architectures
On Tue, 2023-10-03 at 10:18 -0700, Sohil Mehta wrote:
> > If you like, I can pick this up for 6.7 through the asm-generic
> > tree. If you think this should be part of 6.6, I would suggest
> > to merge it through the tree that originally contained the
> > syscall code.
> >
>
> Dave, Ingo, would you prefer to take this patch through 6.6 or defer
> it
> until 6.7?
>
> It's not necessarily a fix but it does help finish up the shstk
> syscall
> added with 6.6. Also, it might help reduce some merge conflicts later
> if
> newer syscalls are being added during the 6.7 window.
Hi Arnd,
It doesn't look like anyone is pouncing on the syscall number in linux-
next currently. It might be nice to have this patch go through linux-
next since it touches so many architectures. And it sounds like x86
folk are ok with this, so if you could pick it up for 6.7 that would be
great. Thanks!
Powered by blists - more mailing lists