From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Mehta, Sohil" <sohil.mehta@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>
Cc: "svens@linux.ibm.com" <svens@linux.ibm.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"schwab@linux-m68k.org" <schwab@linux-m68k.org>,
"brgerst@gmail.com" <brgerst@gmail.com>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"monstr@monstr.eu" <monstr@monstr.eu>,
"borntraeger@linux.ibm.com" <borntraeger@linux.ibm.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"christophe.leroy@csgroup.eu" <christophe.leroy@csgroup.eu>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
"dalias@libc.org" <dalias@libc.org>, "lukas.bulwahn@gmail.com" <>
Subject: Re: [PATCH 2/2] arch: Reserve map_shadow_stack() syscall number for all architectures
Date: Mon, 11 Sep 2023 21:10:26 +0000 [thread overview]
Message-ID: <8b7106881fa227a64b4e951c6b9240a7126ac4a2.camel@intel.com> (raw)
In-Reply-To: <20230911180210.1060504-3-sohil.mehta@intel.com>
On Mon, 2023-09-11 at 18:02 +0000, Sohil Mehta wrote:
> diff --git a/arch/powerpc/kernel/syscalls/syscall.tbl
> b/arch/powerpc/kernel/syscalls/syscall.tbl
> index 20e50586e8a2..2767b8a42636 100644
> --- a/arch/powerpc/kernel/syscalls/syscall.tbl
> +++ b/arch/powerpc/kernel/syscalls/syscall.tbl
> @@ -539,3 +539,4 @@
> 450 nospu set_mempolicy_home_node sys_set_mempolicy_hom
> e_node
> 451 common cachestat sys_cachestat
> 452 common fchmodat2 sys_fchmodat2
> +453 common map_shadow_stack sys_map_shadow_stack
I noticed in powerpc, the not implemented syscalls are manually mapped
to sys_ni_syscall. It also has some special extra sys_ni_syscall()
implementation bits to handle both ARCH_HAS_SYSCALL_WRAPPER and
!ARCH_HAS_SYSCALL_WRAPPER. So wondering if it might need special
treatment. Did you see those parts?
next prev parent reply other threads:[~2023-09-11 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 18:02 [PATCH 0/2] arch: Sync all syscall tables with 2 newly added system calls Sohil Mehta
2023-09-11 18:02 ` [PATCH 1/2] tools headers UAPI: Sync fchmodat2() syscall table entries Sohil Mehta
2023-09-11 18:02 ` [PATCH 2/2] arch: Reserve map_shadow_stack() syscall number for all architectures Sohil Mehta
2023-09-11 21:10 ` Edgecombe, Rick P [this message]
2023-09-13 19:18 ` Sohil Mehta
2023-09-13 22:05 ` Edgecombe, Rick P
2023-09-14 12:26 ` Michael Ellerman
2023-09-13 19:32 ` [PATCH 0/2] arch: Sync all syscall tables with 2 newly added system calls Sohil Mehta
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=8b7106881fa227a64b4e951c6b9240a7126ac4a2.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=borntraeger@linux.ibm.com \
--cc=brgerst@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dalias@libc.org \
--cc=dave.hansen@linux.intel.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=monstr@monstr.eu \
--cc=schwab@linux-m68k.org \
--cc=sohil.mehta@intel.com \
--cc=svens@linux.ibm.com \
--cc=x86@kernel.org \
/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