From: Kees Cook <keescook@chromium.org>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: luto@kernel.org, Rich Felker <dalias@libc.org>,
tglx@linutronix.de, christian.brauner@ubuntu.com,
peterz@infradead.org, willy@infradead.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-kselftest@vger.kernel.org, x86@kernel.org,
gofmanp@gmail.com, kernel@collabora.com
Subject: Re: [PATCH v7 3/7] kernel: Implement selective syscall userspace redirection
Date: Fri, 20 Nov 2020 16:18:55 -0800 [thread overview]
Message-ID: <202011201618.62E507D@keescook> (raw)
In-Reply-To: <87a6vdmedy.fsf@collabora.com>
On Thu, Nov 19, 2020 at 12:43:05PM -0500, Gabriel Krisman Bertazi wrote:
> The existing interface could be extended with a flags field as part of
> the opcode passed in argument 2, which is currently reserved, and then
> return a FD, just like seccomp(2) does. So it is not like the current
> patches couldn't be extended in the future if needed, unless I'm
> mistaken.
Yes, I'd prefer this series go in as-is, and if there is a need for
extending the API, arg2 can have more values added.
--
Kees Cook
next prev parent reply other threads:[~2020-11-21 0:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 3:28 [PATCH v7 0/7] Syscall User Dispatch Gabriel Krisman Bertazi
2020-11-18 3:28 ` [PATCH v7 1/7] x86: vdso: Expose sigreturn address on vdso to the kernel Gabriel Krisman Bertazi
2020-11-18 3:28 ` [PATCH v7 2/7] signal: Expose SYS_USER_DISPATCH si_code type Gabriel Krisman Bertazi
2020-11-18 3:28 ` [PATCH v7 3/7] kernel: Implement selective syscall userspace redirection Gabriel Krisman Bertazi
2020-11-19 12:36 ` Peter Zijlstra
2020-11-19 17:43 ` Gabriel Krisman Bertazi
2020-11-21 0:18 ` Kees Cook [this message]
2020-11-22 4:01 ` Andy Lutomirski
2020-11-18 3:28 ` [PATCH v7 4/7] entry: Support Syscall User Dispatch on common syscall entry Gabriel Krisman Bertazi
2020-11-18 3:28 ` [PATCH v7 5/7] selftests: Add kselftest for syscall user dispatch Gabriel Krisman Bertazi
2020-11-18 3:28 ` [PATCH v7 6/7] selftests: Add benchmark " Gabriel Krisman Bertazi
2020-11-18 3:28 ` [PATCH v7 7/7] docs: Document Syscall User Dispatch Gabriel Krisman Bertazi
2020-11-18 8:48 ` Florian Weimer
2020-11-18 17:02 ` Gabriel Krisman Bertazi
2020-11-18 8:47 ` [PATCH v7 0/7] " Florian Weimer
2020-11-18 17:01 ` Gabriel Krisman Bertazi
2020-11-18 17:22 ` Florian Weimer
2020-11-19 12:38 ` Peter Zijlstra
2020-11-21 0:24 ` Kees Cook
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=202011201618.62E507D@keescook \
--to=keescook@chromium.org \
--cc=christian.brauner@ubuntu.com \
--cc=dalias@libc.org \
--cc=gofmanp@gmail.com \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).