From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753324AbdAZQ30 (ORCPT ); Thu, 26 Jan 2017 11:29:26 -0500 Received: from mail-wj0-f176.google.com ([209.85.210.176]:35277 "EHLO mail-wj0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752702AbdAZQ3Z (ORCPT ); Thu, 26 Jan 2017 11:29:25 -0500 Reply-To: nicolas.dichtel@6wind.com Subject: Re: [PATCH v4 3/7] x86: put msr-index.h in uapi References: <1484304406-10820-1-git-send-email-nicolas.dichtel@6wind.com> <1485183521-13002-1-git-send-email-nicolas.dichtel@6wind.com> <1485183521-13002-4-git-send-email-nicolas.dichtel@6wind.com> <20170123165245.7zy7nf3cx5o4vvh3@pd.tnic> <20170123171732.i3qfbcsqzznppe5m@pd.tnic> <20170123172103.GB28446@infradead.org> <20170123172627.32zcbntwo7nmd5rf@pd.tnic> To: Borislav Petkov , Christoph Hellwig Cc: arnd@arndb.de, mmarek@suse.com, linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, airlied@linux.ie, davem@davemloft.net, linux@armlinux.org.uk, slash.tmp@free.fr, daniel.vetter@ffwll.ch, rmk+kernel@armlinux.org.uk, msalter@redhat.com, jengelh@inai.de, tklauser@distanz.ch, mpe@ellerman.id.au, mingo@kernel.org, hpa@zytor.com From: Nicolas Dichtel Organization: 6WIND Message-ID: <1f363058-86ed-7b37-7497-8c370f33d508@6wind.com> Date: Thu, 26 Jan 2017 17:02:01 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20170123172627.32zcbntwo7nmd5rf@pd.tnic> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 23/01/2017 à 18:26, Borislav Petkov a écrit : > On Mon, Jan 23, 2017 at 09:21:03AM -0800, Christoph Hellwig wrote: >> Or keep the exported version as-is and never changed it, and use >> a different copy for the kernel itself. > > Yeah, that's a good idea, thanks Christoph. > > I guess we'll have to do that if something in userspace has put its > sticky fingers on that file and cannot be fixed. Which I hardly doubt > but we can't break that damn userspace. > So do you agree with the current patch (a build-fix is also needed :/)?