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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 17 Jul 2014 14:39:46 -0700 From: Andy Lutomirski <luto@...capital.net> To: James Morris <james.l.morris@...cle.com> Cc: Kees Cook <keescook@...omium.org>, Oleg Nesterov <oleg@...hat.com>, LKML <linux-kernel@...r.kernel.org>, Alexei Starovoitov <ast@...mgrid.com>, "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>, Andrew Morton <akpm@...ux-foundation.org>, Daniel Borkmann <dborkman@...hat.com>, Will Drewry <wad@...omium.org>, Julien Tinnes <jln@...omium.org>, David Drysdale <drysdale@...gle.com>, Linux API <linux-api@...r.kernel.org>, "x86@...nel.org" <x86@...nel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Linux MIPS Mailing List <linux-mips@...ux-mips.org>, linux-arch <linux-arch@...r.kernel.org>, linux-security-module <linux-security-module@...r.kernel.org> Subject: Re: [PATCH v10 0/11] seccomp: add thread sync ability On Mon, Jul 14, 2014 at 6:53 PM, James Morris <james.l.morris@...cle.com> wrote: > On 07/15/2014 04:59 AM, Kees Cook wrote: >> >> Hi James, >> >> Is this series something you would carry in the security-next tree? >> That has traditionally been where seccomp features have landed in the >> past. >> >> -Kees >> >> >> On Fri, Jul 11, 2014 at 10:55 AM, Kees Cook <keescook@...omium.org> wrote: >>> >>> On Fri, Jul 11, 2014 at 9:49 AM, Oleg Nesterov <oleg@...hat.com> wrote: >>>> >>>> On 07/10, Kees Cook wrote: >>>>> >>>>> >>>>> This adds the ability for threads to request seccomp filter >>>>> synchronization across their thread group (at filter attach time). >>>>> For example, for Chrome to make sure graphic driver threads are fully >>>>> confined after seccomp filters have been attached. >>>>> >>>>> To support this, locking on seccomp changes via thread-group-shared >>>>> sighand lock is introduced, along with refactoring of no_new_privs. >>>>> Races >>>>> with thread creation are handled via delayed duplication of the seccomp >>>>> task struct field and cred_guard_mutex. >>>>> >>>>> This includes a new syscall (instead of adding a new prctl option), >>>>> as suggested by Andy Lutomirski and Michael Kerrisk. >>>> >>>> >>>> I do not not see any problems in this version, >>> >>> >>> Awesome! Thank you for all the reviews. :) If Andy and Michael are >>> happy with this too, I think this is in good shape. \o/ >>> >>> -Kees >>> >>>> >>>> Reviewed-by: Oleg Nesterov <oleg@...hat.com> >>>> >>> >>> >>> >>> -- >>> Kees Cook >>> Chrome OS Security >> >> >> >> > > Yep, certainly. > Any ETA? I'm currently blocking on having stable commit hashes for these. If you're planning on pulling from Kees' tree instead of importing the patches, I can work with that, too. Thanks, Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists