lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 16 Jul 2020 22:29:35 +0200
From:   Christian Brauner <christian.brauner@...ntu.com>
To:     Kees Cook <keescook@...omium.org>
Cc:     Gabriel Krisman Bertazi <krisman@...labora.com>,
        Andy Lutomirski <luto@...nel.org>,
        Matthew Wilcox <willy@...radead.org>, tglx@...utronix.de,
        linux-kernel@...r.kernel.org, kernel@...labora.com,
        gofmanp@...il.com, linux-api@...r.kernel.org, x86@...nel.org,
        linux-kselftest@...r.kernel.org, shuah@...nel.org, jannh@...gle.com
Subject: Re: [PATCH v4 0/2] Syscall User Redirection

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). :)

Christian

Powered by blists - more mailing lists