Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754881AbbB0O5K (ORCPT ); Fri, 27 Feb 2015 09:57:10 -0500 Received: from smtp.citrix.com ([66.165.176.89]:49792 "EHLO SMTP.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754632AbbB0O5G (ORCPT ); Fri, 27 Feb 2015 09:57:06 -0500 X-IronPort-AV: E=Sophos;i="5.09,660,1418083200"; d="scan'208";a="238344770" Message-ID: <54F08524.3010703@citrix.com> Date: Fri, 27 Feb 2015 14:54:28 +0000 From: David Vrabel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0 MIME-Version: 1.0 To: Juergen Gross , , , , , Subject: Re: [PATCH] xen: correct bug in p2m list initialization References: <1425048329-6797-1-git-send-email-jgross@suse.com> In-Reply-To: <1425048329-6797-1-git-send-email-jgross@suse.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-DLP: MIA2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1032 Lines: 24 On 27/02/15 14:45, Juergen Gross wrote: > Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to > linear virtual mapped sparse p2m list") introduced an error. > > During initialization of the p2m list a p2m identity area mapped by > a complete identity pmd entry has to be split up into smaller chunks > sometimes, if a non-identity pfn is introduced in this area. > > If this non-identity pfn is not at index 0 of a p2m page the new > p2m page needed is initialized with wrong identity entries, as the > identity pfns don't start with the value corresponding to index 0, > but with the initial non-identity pfn. This results in weird wrong > mappings. > > Correct the wrong initialization by starting with the correct pfn. Applied to stable/for-linus-4.0, thanks. David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/