public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Rick Edgecombe" <rick.p.edgecombe@intel.com>,
	"Sohil Mehta" <sohil.mehta@intel.com>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"Ingo Molnar" <mingo@redhat.com>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>
Cc: "Christian Borntraeger" <borntraeger@linux.ibm.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Helge Deller" <deller@gmx.de>,
	"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
	"Ian Rogers" <irogers@google.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"David S . Miller" <davem@davemloft.net>,
	"Andy Lutomirski" <luto@kernel.org>,
	"Max Filippov" <jcmvbkbc@gmail.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"Yoshinori Sato" <ysato@users.sourceforge.jp>,
	"Adrian Hunter" <adrian.hunter@intel.com>,
	"chris@zankel.net" <chris@zankel.net>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Brian Gerst" <brgerst@gmail.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"Mark Brown" <broonie@kernel.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"x86@kernel.org" <x86@kernel.org>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Ivan Kokshaysky" <ink@jurassic.park.msu.ru>,
	"Borislav Petkov" <bp@alien8.de>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"Namhyung Kim" <namhyung@kernel.org>,
	"Jiri Olsa" <jolsa@kernel.org>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Michal Simek" <monstr@monstr.eu>,
	"linux-m68k@lists.linux-m68k.org"
	<linux-m68k@lists.linux-m68k.org>,
	"Deepak Gupta" <debug@rivosinc.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Will Deacon" <will@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	"gor@linux.ibm.com" <gor@linux.ibm.com>,
	"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
	"Matt Turner" <mattst88@gmail.com>,
	"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
	"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
	"Arnaldo Carvalho de Melo" <acme@kernel.org>,
	"Sergei Trofimovich" <slyich@gmail.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
	"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Rohan McLure" <rmclure@linux.ibm.com>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
	"Sven Schnelle" <svens@linux.ibm.com>,
	"Rich Felker" <dalias@libc.org>,
	"Andreas Schwab" <schwab@linux-m68k.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH v2] arch: Reserve map_shadow_stack() syscall number for all architectures
Date: Fri, 06 Oct 2023 22:29:32 +0200	[thread overview]
Message-ID: <5d397fe4-a520-4336-b966-29bc5b798236@app.fastmail.com> (raw)
In-Reply-To: <3bd9a85c6f10279af6372cf17064978ad38c18b3.camel@intel.com>

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

  reply	other threads:[~2023-10-06 20:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 18:58 [PATCH v2] arch: Reserve map_shadow_stack() syscall number for all architectures Sohil Mehta
2023-09-14 22:08 ` Edgecombe, Rick P
2023-09-15  3:23 ` Michael Ellerman
2023-10-03 16:35 ` Sohil Mehta
2023-10-03 16:54   ` Arnd Bergmann
2023-10-03 17:18     ` Sohil Mehta
2023-10-06 20:01       ` Edgecombe, Rick P
2023-10-06 20:29         ` Arnd Bergmann [this message]
2023-10-06 20:36           ` Sohil Mehta
2023-10-03 17:19 ` Geert Uytterhoeven
2023-10-04  7:22 ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5d397fe4-a520-4336-b966-29bc5b798236@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=chris@zankel.net \
    --cc=christophe.leroy@csgroup.eu \
    --cc=dalias@libc.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=debug@rivosinc.com \
    --cc=deller@gmx.de \
    --cc=ebiederm@xmission.com \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=irogers@google.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=luto@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mattst88@gmail.com \
    --cc=mingo@redhat.com \
    --cc=monstr@monstr.eu \
    --cc=mpe@ellerman.id.au \
    --cc=namhyung@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=richard.henderson@linaro.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=rmclure@linux.ibm.com \
    --cc=schwab@linux-m68k.org \
    --cc=slyich@gmail.com \
    --cc=sohil.mehta@intel.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=tsbogend@alpha.franken.de \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox