Re: [PATCH v2] arch: Reserve map_shadow_stack() syscall number for all architectures
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "Rick Edgecombe" <rick.p.edgecombe@xxxxxxxxx>, "Sohil Mehta" <sohil.mehta@xxxxxxxxx>, "Dave Hansen" <dave.hansen@xxxxxxxxxxxxxxx>, "Ingo Molnar" <mingo@xxxxxxxxxx>, Linux-Arch <linux-arch@xxxxxxxxxxxxxxx>, "linux-api@xxxxxxxxxxxxxxx" <linux-api@xxxxxxxxxxxxxxx>
- Subject: Re: [PATCH v2] arch: Reserve map_shadow_stack() syscall number for all architectures
- From: "Arnd Bergmann" <arnd@xxxxxxxx>
- Date: Fri, 06 Oct 2023 22:29:32 +0200
- Cc: "Christian Borntraeger" <borntraeger@xxxxxxxxxxxxx>, "Thomas Gleixner" <tglx@xxxxxxxxxxxxx>, "Helge Deller" <deller@xxxxxx>, "Lukas Bulwahn" <lukas.bulwahn@xxxxxxxxx>, "Ian Rogers" <irogers@xxxxxxxxxx>, "Alexander Gordeev" <agordeev@xxxxxxxxxxxxx>, "David S . Miller" <davem@xxxxxxxxxxxxx>, "Andy Lutomirski" <luto@xxxxxxxxxx>, "Max Filippov" <jcmvbkbc@xxxxxxxxx>, "Russell King" <linux@xxxxxxxxxxxxxxx>, "Yoshinori Sato" <ysato@xxxxxxxxxxxxx>, "Adrian Hunter" <adrian.hunter@xxxxxxxxx>, "chris@xxxxxxxxxx" <chris@xxxxxxxxxx>, "Heiko Carstens" <hca@xxxxxxxxxxxxx>, "Catalin Marinas" <catalin.marinas@xxxxxxx>, "Peter Zijlstra" <peterz@xxxxxxxxxxxxx>, "Brian Gerst" <brgerst@xxxxxxxxx>, "linuxppc-dev@xxxxxxxxxxxxxxxx" <linuxppc-dev@xxxxxxxxxxxxxxxx>, "Mark Brown" <broonie@xxxxxxxxxx>, "linux-s390@xxxxxxxxxxxxxxx" <linux-s390@xxxxxxxxxxxxxxx>, "linux-mips@xxxxxxxxxxxxxxx" <linux-mips@xxxxxxxxxxxxxxx>, "Christophe Leroy" <christophe.leroy@xxxxxxxxxx>, "x86@xxxxxxxxxx" <x86@xxxxxxxxxx>, "Michael Ellerman" <mpe@xxxxxxxxxxxxxx>, "Thomas Bogendoerfer" <tsbogend@xxxxxxxxxxxxxxxx>, "Ivan Kokshaysky" <ink@xxxxxxxxxxxxxxxxxxxx>, "Borislav Petkov" <bp@xxxxxxxxx>, "Geert Uytterhoeven" <geert@xxxxxxxxxxxxxx>, "Randy Dunlap" <rdunlap@xxxxxxxxxxxxx>, "Mark Rutland" <mark.rutland@xxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "linux-ia64@xxxxxxxxxxxxxxx" <linux-ia64@xxxxxxxxxxxxxxx>, "Namhyung Kim" <namhyung@xxxxxxxxxx>, "Jiri Olsa" <jolsa@xxxxxxxxxx>, "Nicholas Piggin" <npiggin@xxxxxxxxx>, "Michal Simek" <monstr@xxxxxxxxx>, "linux-m68k@xxxxxxxxxxxxxxxxxxxx" <linux-m68k@xxxxxxxxxxxxxxx>, "Deepak Gupta" <debug@xxxxxxxxxxxx>, "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>, "Richard Henderson" <richard.henderson@xxxxxxxxxx>, "Will Deacon" <will@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, "gor@xxxxxxxxxxxxx" <gor@xxxxxxxxxxxxx>, "Alexander Shishkin" <alexander.shishkin@xxxxxxxxxxxxxxx>, "Matt Turner" <mattst88@xxxxxxxxx>, "John Paul Adrian Glaubitz" <glaubitz@xxxxxxxxxxxxxxxxxxx>, "linux-parisc@xxxxxxxxxxxxxxx" <linux-parisc@xxxxxxxxxxxxxxx>, "Arnaldo Carvalho de Melo" <acme@xxxxxxxxxx>, "Sergei Trofimovich" <slyich@xxxxxxxxx>, "linux-arm-kernel@xxxxxxxxxxxxxxxxxxx" <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, "linux-alpha@xxxxxxxxxxxxxxx" <linux-alpha@xxxxxxxxxxxxxxx>, "James E . J . Bottomley" <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>, "Rohan McLure" <rmclure@xxxxxxxxxxxxx>, "linux-sh@xxxxxxxxxxxxxxx" <linux-sh@xxxxxxxxxxxxxxx>, "Sven Schnelle" <svens@xxxxxxxxxxxxx>, "Rich Felker" <dalias@xxxxxxxx>, "Andreas Schwab" <schwab@xxxxxxxxxxxxxx>, "Andrew Morton" <akpm@xxxxxxxxxxxxxxxxxxxx>, "sparclinux@xxxxxxxxxxxxxxx" <sparclinux@xxxxxxxxxxxxxxx>, "linux-perf-users@xxxxxxxxxxxxxxx" <linux-perf-users@xxxxxxxxxxxxxxx>
- Feedback-id: i56a14606:Fastmail
- In-reply-to: <3bd9a85c6f10279af6372cf17064978ad38c18b3.camel@intel.com>
- References: <20230914185804.2000497-1-sohil.mehta@intel.com> <487836fc-7c9f-2662-66a4-fa5e3829cf6b@intel.com> <231994b0-ca11-4347-8d93-ce66fdbe3d25@app.fastmail.com> <622b95d8-f8ad-5bd4-0145-d6aed2e3c07d@intel.com> <3bd9a85c6f10279af6372cf17064978ad38c18b3.camel@intel.com>
- User-agent: Cyrus-JMAP/3.9.0-alpha0-958-g1b1b911df8-fm-20230927.002-g1b1b911d
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
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]