From: Carlos O'Donell <firstname.lastname@example.org> To: Gabriel Krisman Bertazi <email@example.com>, Christian Brauner <firstname.lastname@example.org> Cc: Kees Cook <email@example.com>, Andy Lutomirski <firstname.lastname@example.org>, Matthew Wilcox <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Re: [PATCH v4 0/2] Syscall User Redirection Date: Thu, 16 Jul 2020 17:06:14 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 7/16/20 4:30 PM, Gabriel Krisman Bertazi wrote: > Christian Brauner <email@example.com> writes: > >> On Thu, Jul 16, 2020 at 01:25:43PM -0700, Kees Cook wrote: >>> On Thu, Jul 16, 2020 at 10:22:34PM +0200, Christian Brauner wrote: >>>> On Thu, Jul 16, 2020 at 01:04:38PM -0700, Kees Cook wrote: >>>>> On Thu, Jul 16, 2020 at 03:31:39PM -0400, Gabriel Krisman Bertazi wrote: >>>>>> This is v4 of Syscall User Redirection. The implementation itself is >>>>>> not modified from v3, it only applies the latest round of reviews to the >>>>>> selftests. >>>>>> >>>>>> __NR_syscalls is not really exported in header files other than >>>>>> asm-generic for every architecture, so it felt safer to optionally >>>>>> expose it with a fallback to a high value. >>>>>> >>>>>> Also, I didn't expose tests for PR_GET as that is not currently >>>>>> implemented. If possible, I'd have it supported by a future patchset, >>>>>> since it is not immediately necessary to support this feature. >>>>> >>>>> Thanks! That all looks good to me. >>>> >>>> Don't have any problem with this but did this ever get exposure on >>>> linux-api? This is the first time I see this pop up. >>> >>> I thought I'd added it to CC in the past, but that might have been other >>> recent unrelated threads. Does this need a full repost there too, you >>> think? >> >> Nah, wasn't my intention to force a repost. Seems that several people >> have looked this over. :) Just curious why it didn't get to linux-api >> and we know quite some people who only do look at linux-api (for sanity). :) > > That's my mistake. I didn't think about it when submitting :( > > If this get re-spinned again I will make sure to CC linux-api. Thank you! It helps C library implementors stay up to date and comment on changes that impact userspace ABIs and APIs. This patch set was new to me. Interesting new feature. -- Cheers, Carlos.
next prev parent reply other threads:[~2020-07-16 21:06 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-16 19:31 Gabriel Krisman Bertazi 2020-07-16 19:31 ` [PATCH v4 1/2] kernel: Implement selective syscall userspace redirection Gabriel Krisman Bertazi 2020-07-16 21:06 ` Matthew Wilcox 2020-07-16 21:26 ` Kees Cook 2020-07-17 0:20 ` Andy Lutomirski 2020-07-17 2:15 ` Gabriel Krisman Bertazi 2020-07-17 4:48 ` Andy Lutomirski 2020-07-21 12:06 ` Mark Rutland 2020-07-20 9:23 ` Thomas Gleixner 2020-07-20 9:44 ` Will Deacon 2020-07-20 10:08 ` Thomas Gleixner 2020-07-20 13:46 ` Gabriel Krisman Bertazi 2020-07-16 19:31 ` [PATCH v4 2/2] selftests: Add kselftest for syscall user dispatch Gabriel Krisman Bertazi 2020-07-16 20:04 ` [PATCH v4 0/2] Syscall User Redirection Kees Cook 2020-07-16 20:22 ` Christian Brauner 2020-07-16 20:25 ` Kees Cook 2020-07-16 20:29 ` Christian Brauner 2020-07-16 20:30 ` Gabriel Krisman Bertazi 2020-07-16 21:06 ` Carlos O'Donell [this message] 2020-08-02 12:01 ` Pavel Machek 2020-08-04 14:26 ` Gabriel Krisman Bertazi
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v4 0/2] Syscall User Redirection' \ /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
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).