From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753681Ab1JOQ7p (ORCPT ); Sat, 15 Oct 2011 12:59:45 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:41082 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752925Ab1JOQ7o (ORCPT ); Sat, 15 Oct 2011 12:59:44 -0400 Date: Sat, 15 Oct 2011 18:57:57 +0200 From: Ingo Molnar To: richard -rw- weinberger Cc: Andrew Lutomirski , Linus Torvalds , Adrian Bunk , "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC] fixing the UML failure root cause Message-ID: <20111015165757.GA29782@elte.hu> References: <20111010114840.GC17079@elte.hu> <20111011062253.GA3589@elte.hu> <4E947BC9.7040805@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * richard -rw- weinberger wrote: > On Fri, Oct 14, 2011 at 10:17 PM, Andrew Lutomirski wrote: > > On Fri, Oct 14, 2011 at 12:53 PM, richard -rw- weinberger > > wrote: > >> On Tue, Oct 11, 2011 at 7:24 PM, Andrew Lutomirski wrote: > >>> What do you think of this approach?  If it seems good, I'll finish the > >>> patch and submit it. > >>> > >>> With this patch applied, UML appears to work, but it fills the log with > >>> exploit attempt warnings.  Any ideas on what to do about that? > >>> > >> > >> I can confirm that this patch works. > >> And I really like vsyscall=emulate because with that UML can trap vsyscalls. :-) > > > > Are you sure you don't mean vsyscall=native?  I suspect that UML can't > > actually trap vsyscalls in emulate mode right now, although that ought > > to be fixable. > > > > §/%)"&!, you are so right! > I missed that vsyscall=native is the default setting now. > Sorry for the confusion. Switch back to vsyscall=native was just a temporary ABI fix for v3.1 - we'd like to switch to vsyscall=emulate again ASAP (possibly in v3.2), once Andrew is done with the patch and everyone is happy with it. Thanks, Ingo