linux-kernel - Re: [3.1 REGRESSION] Commit 5cec93c216db77c45f7ce970d46283bcb1933884 breaks the Chromium seccomp sandbox

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAObL_7GEeF37rHkWYGDR3B596j8WnOJXB2dLD0ZdXgwNhU3Jkw@mail.gmail.com>
Date:	Sun, 13 Nov 2011 20:00:13 -0800
From:	Andrew Lutomirski <luto@....edu>
To:	Nix <nix@...eri.org.uk>
Cc:	linux-kernel@...r.kernel.org, mseaborn@...omium.org
Subject: Re: [3.1 REGRESSION] Commit 5cec93c216db77c45f7ce970d46283bcb1933884
 breaks the Chromium seccomp sandbox

On Sun, Nov 13, 2011 at 6:36 PM, Andrew Lutomirski <luto@....edu> wrote:
>
> The attached patch (in vsyscall=native mode) should help diagnose
> exactly what's wrong.  But I wouldn't be surprised if you can trigger
> the exact same failure on older kernels by doing

Now with actual attachment.

--Andy

View attachment "log_seccomp_kill.patch" of type "text/x-patch" (359 bytes)