From: Jeff Xu <jeffxu@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: akpm@linux-foundation.org, keescook@chromium.org,
jannh@google.com, sroettger@google.com, willy@infradead.org,
gregkh@linuxfoundation.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 v4 2/4] mseal: add mseal syscall
Date: Mon, 8 Jan 2024 08:00:00 -0800 [thread overview]
Message-ID: <CABi2SkXx0bWeqMTb1TRwya6_Hx6NGnMEtycQ56g9S5ORpz7u=Q@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wiy0nHG9+3rXzQa=W8gM8F6-MhsHrs_ZqWaHtjmPK4=FA@mail.gmail.com>
On Sun, Jan 7, 2024 at 10:42 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> One comment:
>
> On Thu, 4 Jan 2024 at 10:51, <jeffxu@chromium.org> wrote:
> >
> > diff --git a/kernel/sys_ni.c b/kernel/sys_ni.c
> > index 9a846439b36a..02280199069b 100644
> > --- a/kernel/sys_ni.c
> > +++ b/kernel/sys_ni.c
> > @@ -193,6 +193,7 @@ COND_SYSCALL(migrate_pages);
> > COND_SYSCALL(move_pages);
> > COND_SYSCALL(set_mempolicy_home_node);
> > COND_SYSCALL(cachestat);
> > +COND_SYSCALL(mseal);
> >
> > COND_SYSCALL(perf_event_open);
> > COND_SYSCALL(accept4);
>
> Move this part to PATCH 1/1, so that it all builds cleanly.
>
Sure, thanks!
-Jeff
> Other than that, this seems all reasonable to me now.
>
> Linus
next prev parent reply other threads:[~2024-01-08 16:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 18:51 [RFC PATCH v4 0/4] Introduce mseal() jeffxu
2024-01-04 18:51 ` [RFC PATCH v4 1/4] mseal: Wire up mseal syscall jeffxu
2024-01-05 7:44 ` Greg KH
2024-01-05 19:37 ` Jeff Xu
2024-01-04 18:51 ` [RFC PATCH v4 2/4] mseal: add " jeffxu
2024-01-07 18:41 ` Linus Torvalds
2024-01-08 16:00 ` Jeff Xu [this message]
2024-01-04 18:51 ` [RFC PATCH v4 3/4] selftest mm/mseal memory sealing jeffxu
2024-01-09 7:17 ` Muhammad Usama Anjum
2024-01-11 3:04 ` Jeff Xu
2024-01-04 18:51 ` [RFC PATCH v4 4/4] mseal:add documentation jeffxu
2024-01-04 23:47 ` Randy Dunlap
2024-01-05 19:37 ` Jeff Xu
2024-01-16 20:13 ` Jonathan Corbet
2024-01-16 20:48 ` Jeff Xu
2024-01-16 22:19 ` Randy Dunlap
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='CABi2SkXx0bWeqMTb1TRwya6_Hx6NGnMEtycQ56g9S5ORpz7u=Q@mail.gmail.com' \
--to=jeffxu@chromium.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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.