From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755123AbaCMTeo (ORCPT ); Thu, 13 Mar 2014 15:34:44 -0400 Received: from terminus.zytor.com ([198.137.202.10]:42263 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754499AbaCMTen (ORCPT ); Thu, 13 Mar 2014 15:34:43 -0400 User-Agent: K-9 Mail for Android In-Reply-To: References: <1394664680-17799-1-git-send-email-stefani@seibold.net> <1394664680-17799-4-git-send-email-stefani@seibold.net> <5320E689.7060607@zytor.com> <5321D45C.7040504@zytor.com> <5321F418.1030304@zytor.com> <5321F72E.7030109@zytor.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: [PATCH 3/3] x86, vdso32: handle 32 bit vDSO larger one page From: "H. Peter Anvin" Date: Thu, 13 Mar 2014 12:33:49 -0700 To: Linus Torvalds , Andy Lutomirski CC: Pavel Emelyanov , Ingo Molnar , Cyrill Gorcunov , "linux-kernel@vger.kernel.org" , Stefani Seibold , Greg KH , Andrea Arcangeli , Andreas Brief , Andi Kleen , John Stultz , Andy Shevchenko , Thomas Gleixner , Martin Runge , the arch/x86 maintainers Message-ID: <8cf1b00c-ef93-4ad0-97f7-53888b50d160@email.android.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org If we have to stick anything in the fixmap it might add well be the real vdso... On March 13, 2014 12:21:54 PM PDT, Linus Torvalds wrote: >On Mar 13, 2014 12:13 PM, "Andy Lutomirski" >wrote: >> >> How? We either set null in AT_SYSINFO_EHDR, we set something simple >> that SuSE is okay with (and compile separate images?) or we set >> something fancy and not relocated, and SuSE crashes. > >Yeah, I was thinking that "something simple is the fixmap space that >suse >would be happy with" > >Keyword being "simple", ie so simple that it's not a maintenance >headache >even if it's different from the "real" vdso. > >But I suspect we don't really need it. > >> On a related note: is it okay to keep the option called >> CONFIG_COMPAT_VDSO but change the default to n? > >Yes. If you start from scratch with a config, you have to get the >options >right. It's just the "I upgraded the kernel, did an oldconfig, and it >doesn't work" case that we should avoid. > >The alternative would be to make a new config name, but then it has to >default to the compatible state (iow no vdso at all by default), >because >that's the rule: make oldconfig should work for people. > >Basically, kernel upgrades should be nobrainers and "just work". > > Linus -- Sent from my mobile phone. Please pardon brevity and lack of formatting.