[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5d397fe4-a520-4336-b966-29bc5b798236@app.fastmail.com>
Date: Fri, 06 Oct 2023 22:29:32 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Rick Edgecombe" <rick.p.edgecombe@...el.com>,
"Sohil Mehta" <sohil.mehta@...el.com>,
"Dave Hansen" <dave.hansen@...ux.intel.com>,
"Ingo Molnar" <mingo@...hat.com>,
Linux-Arch <linux-arch@...r.kernel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>
Cc: "Christian Borntraeger" <borntraeger@...ux.ibm.com>,
"Thomas Gleixner" <tglx@...utronix.de>,
"Helge Deller" <deller@....de>,
"Lukas Bulwahn" <lukas.bulwahn@...il.com>,
"Ian Rogers" <irogers@...gle.com>,
"Alexander Gordeev" <agordeev@...ux.ibm.com>,
"David S . Miller" <davem@...emloft.net>,
"Andy Lutomirski" <luto@...nel.org>,
"Max Filippov" <jcmvbkbc@...il.com>,
"Russell King" <linux@...linux.org.uk>,
"Yoshinori Sato" <ysato@...rs.sourceforge.jp>,
"Adrian Hunter" <adrian.hunter@...el.com>,
"chris@...kel.net" <chris@...kel.net>,
"Heiko Carstens" <hca@...ux.ibm.com>,
"Catalin Marinas" <catalin.marinas@....com>,
"Peter Zijlstra" <peterz@...radead.org>,
"Brian Gerst" <brgerst@...il.com>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"Mark Brown" <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" <christophe.leroy@...roup.eu>,
"x86@...nel.org" <x86@...nel.org>,
"Michael Ellerman" <mpe@...erman.id.au>,
"Thomas Bogendoerfer" <tsbogend@...ha.franken.de>,
"Ivan Kokshaysky" <ink@...assic.park.msu.ru>,
"Borislav Petkov" <bp@...en8.de>,
"Geert Uytterhoeven" <geert@...ux-m68k.org>,
"Randy Dunlap" <rdunlap@...radead.org>,
"Mark Rutland" <mark.rutland@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
"Namhyung Kim" <namhyung@...nel.org>,
"Jiri Olsa" <jolsa@...nel.org>,
"Nicholas Piggin" <npiggin@...il.com>,
"Michal Simek" <monstr@...str.eu>,
"linux-m68k@...ts.linux-m68k.org" <linux-m68k@...ts.linux-m68k.org>,
"Deepak Gupta" <debug@...osinc.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Richard Henderson" <richard.henderson@...aro.org>,
"Will Deacon" <will@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
"gor@...ux.ibm.com" <gor@...ux.ibm.com>,
"Alexander Shishkin" <alexander.shishkin@...ux.intel.com>,
"Matt Turner" <mattst88@...il.com>,
"John Paul Adrian Glaubitz" <glaubitz@...sik.fu-berlin.de>,
"linux-parisc@...r.kernel.org" <linux-parisc@...r.kernel.org>,
"Arnaldo Carvalho de Melo" <acme@...nel.org>,
"Sergei Trofimovich" <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 E . J . Bottomley" <James.Bottomley@...senPartnership.com>,
"Rohan McLure" <rmclure@...ux.ibm.com>,
"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
"Sven Schnelle" <svens@...ux.ibm.com>,
"Rich Felker" <dalias@...c.org>,
"Andreas Schwab" <schwab@...ux-m68k.org>,
"Andrew Morton" <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 Fri, Oct 6, 2023, at 22:01, Edgecombe, Rick P wrote:
> 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!
Ok, I picked it up now, should be in linux-next starting next week.
Arnd
Powered by blists - more mailing lists