Return-path: Received: from mail-ww0-f44.google.com ([74.125.82.44]:45199 "EHLO mail-ww0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753692Ab1KUWMR convert rfc822-to-8bit (ORCPT ); Mon, 21 Nov 2011 17:12:17 -0500 MIME-Version: 1.0 In-Reply-To: <201111212249.31196.rjw@sisk.pl> References: <201111212249.31196.rjw@sisk.pl> From: Linus Torvalds Date: Mon, 21 Nov 2011 14:11:54 -0800 Message-ID: (sfid-20111121_231241_057942_2CD6D34C) Subject: Re: 3.2-rc2+: Reported regressions from 3.0 and 3.1 To: "Rafael J. Wysocki" , Andy Lutomirski Cc: Linux Kernel Mailing List , Maciej Rutecki , Florian Mickler , Andrew Morton , Kernel Testers List , Network Development , Linux ACPI , Linux PM List , Linux SCSI List , Linux Wireless List , DRI Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Nov 21, 2011 at 1:49 PM, Rafael J. Wysocki wrote: > > Subject ? ?: [3.1 REGRESSION] Commit 5cec93c216db77c45f7ce970d46283bcb1933884 breaks the Chromium seccomp sandbox > Submitter ?: Nix > Date ? ? ? : 2011-11-14 0:40 > Message-ID : 8762inleno.fsf@spindle.srvr.nix > References : http://marc.info/?l=linux-kernel&m=132123396226377&w=2 So this should be fixed by commit 2b666859ec32 ("x86: Default to vsyscall=native for now"), since we disabled the vsyscall emulation because it broken UML too. Of course, the chromium seccomp thing might re-surface with the patches that enable the emulation (with better emulation), which Andy is still working on, and that I was planning on merging for 3.3. Andy, it migth be worth contacting Nix and having him test whether your fixed emulation works for chromium too. Linus