From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755737AbcANUvl (ORCPT ); Thu, 14 Jan 2016 15:51:41 -0500 Received: from youngberry.canonical.com ([91.189.89.112]:47415 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755621AbcANUvi convert rfc822-to-8bit (ORCPT ); Thu, 14 Jan 2016 15:51:38 -0500 Message-ID: <1452804690.29924.3.camel@fourier> Subject: Re: [PATCH 3.12 25/91] x86/setup: Extend low identity map to cover whole kernel range From: Kamal Mostafa To: Luis Henriques Cc: Matt Fleming , Paolo Bonzini , Jiri Slaby , stable@vger.kernel.org, linux-kernel@vger.kernel.org, Borislav Petkov , "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , Andy Lutomirski , Greg Kroah-Hartman Date: Thu, 14 Jan 2016 12:51:30 -0800 In-Reply-To: <20160106142237.GA16910@ares> References: <2c131230744f95abdbecffbf19de6bfa8a889253.1452015822.git.jslaby@suse.cz> <568CF0B8.7090809@redhat.com> <20160106110031.GA2671@codeblueprint.co.uk> <20160106112455.GA14364@ares> <20160106133155.GD2671@codeblueprint.co.uk> <20160106142237.GA16910@ares> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2016-01-06 at 14:22 +0000, Luis Henriques wrote: > [ Adding Greg and Kamal ] > > On Wed, Jan 06, 2016 at 01:31:55PM +0000, Matt Fleming wrote: > > On Wed, 06 Jan, at 11:24:55AM, Luis Henriques wrote: > > > On Wed, Jan 06, 2016 at 11:00:31AM +0000, Matt Fleming wrote: > > > > On Wed, 06 Jan, at 11:47:20AM, Paolo Bonzini wrote: > > > > > > > > > > Without testing the problematic scenario explicitly (32-bit UEFI > > > > > kernel), I think this patch and 26/91 should not be backported to > > > > > kernels that do not have 23a0d4e8fa6d. > > > > > > > > I tend to agree. > > > > > > I can see these 2 commits in kernels as old as 3.10 (which definitely do > > > not include 23a0d4e8fa6d). Does this mean these should be reverted from > > > stable kernels that already include these patches? Or would you rather > > > recommend to backport 23a0d4e8fa6d? > > > > That depends on your appetite for risk ;-) > > > > Heh, I guess stable kernels aren't really about appetite for risk :-) > > > 23a0d4e8fa6d does fix a legitimate bug, albeit one that no one seems > > to have ever hit. Personally, I'd go for backporting 23a0d4e8fa6d. > > This commit doesn't seem to be too bad to backport. I'm attaching 2 > backports: > > - one is for the 3.16 stable kernel, > - the other can be applied to 3.10, 3.12 and 3.13 > > (For the other kernels, I believe 23a0d4e8fa6d will be a clean > cherry-pick.) > > Cheers, > -- > Luís Queued up for 3.13 and 3.19 -stable. Thanks, Luis! -Kamal