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: Sat, 19 Jul 2014 17:50:55 -0400 From: Theodore Ts'o <tytso@....edu> To: Kees Cook <keescook@...omium.org> Cc: James Morris <jmorris@...ei.org>, linux-security-module <linux-security-module@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, Andy Lutomirski <luto@...capital.net>, Oleg Nesterov <oleg@...hat.com>, Will Drewry <wad@...omium.org>, Julien Tinnes <jln@...omium.org>, David Drysdale <drysdale@...gle.com> Subject: Re: [PULL] seccomp update (3.17) On Sat, Jul 19, 2014 at 07:49:55AM -0700, Kees Cook wrote: > > No worries -- the only user of the seccomp syscall that I know of is > the seccomp regression testing suite, and that'd be trivially to fix. > > I would note that the seccomp series includes adding the syscall also > to ARM and MIPS, so from a collision fixing perspective, it may be > fewer edits to fix getrandom instead. :) I've only wired up x86 and x86_64 for getrandom(2) so far. I had assumed the ARM and MIPS folks would prefer to wire up new syscalls on their own... - Ted -- 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