From: Geert Uytterhoeven <geert@linux-m68k.org>
To: jeffxu@chromium.org
Cc: akpm@linux-foundation.org, keescook@chromium.org,
jannh@google.com, sroettger@google.com, willy@infradead.org,
gregkh@linuxfoundation.org, torvalds@linux-foundation.org,
usama.anjum@collabora.com, jeffxu@google.com,
jorgelo@chromium.org, groeck@chromium.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, pedro.falcato@gmail.com,
dave.hansen@intel.com, linux-hardening@vger.kernel.org,
deraadt@openbsd.org
Subject: Re: [RFC PATCH v5 1/4] mseal: Wire up mseal syscall
Date: Tue, 9 Jan 2024 19:32:30 +0100 [thread overview]
Message-ID: <CAMuHMdWhHuhviuK=Ku-HUm_y9SzVPuubjiNfHS_jQMk4NRxJxg@mail.gmail.com> (raw)
In-Reply-To: <20240109154547.1839886-2-jeffxu@chromium.org>
Hi Jeff,
On Tue, Jan 9, 2024 at 4:46 PM <jeffxu@chromium.org> wrote:
> From: Jeff Xu <jeffxu@chromium.org>
>
> Wire up mseal syscall for all architectures.
>
> Signed-off-by: Jeff Xu <jeffxu@chromium.org>
Thanks for the update!
> --- a/arch/m68k/kernel/syscalls/syscall.tbl
> +++ b/arch/m68k/kernel/syscalls/syscall.tbl
> @@ -456,3 +456,4 @@
> 454 common futex_wake sys_futex_wake
> 455 common futex_wait sys_futex_wait
> 456 common futex_requeue sys_futex_requeue
> +457 common mseal sys_mseal
In the meantime, 457 and 458 are already taken by statmount() and
listmount():
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/m68k/kernel/syscalls/syscall.tbl#n459
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-01-09 18:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 15:45 [RFC PATCH v5 0/4] Introduce mseal() jeffxu
2024-01-09 15:45 ` [RFC PATCH v5 1/4] mseal: Wire up mseal syscall jeffxu
2024-01-09 18:32 ` Geert Uytterhoeven [this message]
2024-01-10 5:10 ` Jeff Xu
2024-01-09 15:45 ` [RFC PATCH v5 2/4] mseal: add " jeffxu
2024-01-09 20:36 ` Matthew Wilcox
2024-01-11 2:58 ` Jeff Xu
2024-01-09 15:45 ` [RFC PATCH v5 3/4] selftest mm/mseal memory sealing jeffxu
2024-01-09 15:45 ` [RFC PATCH v5 4/4] mseal:add documentation jeffxu
2024-01-11 3:16 ` Randy Dunlap
2024-01-11 5:19 ` Jeff Xu
2024-01-09 19:47 ` [RFC PATCH v5 0/4] Introduce mseal() Kees Cook
2024-01-10 5:10 ` Jeff Xu
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='CAMuHMdWhHuhviuK=Ku-HUm_y9SzVPuubjiNfHS_jQMk4NRxJxg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=deraadt@openbsd.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=jeffxu@google.com \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pedro.falcato@gmail.com \
--cc=sroettger@google.com \
--cc=torvalds@linux-foundation.org \
--cc=usama.anjum@collabora.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).