Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp1733813pxb; Thu, 16 Sep 2021 14:17:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyrmMUh1SFFsWW54T0q5aR7DktIp3dYMp0GthcN1UaMEwFuwnSdn63iCgI7+E0/PdEoMYPA X-Received: by 2002:a02:1dc9:: with SMTP id 192mr6097327jaj.92.1631827059231; Thu, 16 Sep 2021 14:17:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631827059; cv=none; d=google.com; s=arc-20160816; b=uHvlV1444yqIul30e2gWFwho5GgEf0XGv6B4DIIvtNGVh+BqDK7J/9DDtJsTwPcg34 E6xRhQpkDa6MD4QGfUxH6a/+zqE4M5yHnY8BvJn70LLX/W2CpzzXyWpnaN+07oVPk7uB ptOX3DqDYRSt+aTMICFeGglwKhFYZ3YUKT2JODORxs8AylyrWKKr6rXn7lfV4mbhDUch hFzObO+KV4U3HoyLgoEVPLYkrvsDjnReXy8YeaFh700+RyWaJ3mMoejrtXO6PyJQ6KQn vLierC48+axbSsFMREmbeBL56p4nxb+E8we16Id2BFFihe4vuOoIWoxtohaPsBNgo1Fp dJbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=oswHMZclWh5+tHy0mj/TWL2ce+cy+5wcy3muWwqWdhA=; b=sf95cMZD5mmQzBf5hARdxY34Xawdv11kDMa8/Yq3DwBN3wdTkHKmHvF4XC9zutXKln gXZS0NdXPkebJrrBrDeZ8lNLWSP8W9a02UMJ/UuW4i17ijklBqety8l1zPDVmx9g0D2W U4tDVo2sVFmziwiisjjxVqvoXJ5fajTGOYW6hwVjZAepQ+iA8n6saeUAFeXxiqSgfNLi vS5occ4VawXTRLxxUkIGz+Kbxp8kHUyjwKbBRLr5cbo54ea9aKSXxn8t59sTTm4AZO5S uE9VSRwPsiv0m90mLm9YSWAEHQlG+4rxlt+JNlOoCuO3Z2m2uc8LDtdDKVVBDBJYUUmw 9rUA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Q1Z2eoc0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a4si3469686ilm.69.2021.09.16.14.17.27; Thu, 16 Sep 2021 14:17:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Q1Z2eoc0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244393AbhIPQfK (ORCPT + 99 others); Thu, 16 Sep 2021 12:35:10 -0400 Received: from mail.kernel.org ([198.145.29.99]:37898 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236996AbhIPQ1a (ORCPT ); Thu, 16 Sep 2021 12:27:30 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id C3FC961529; Thu, 16 Sep 2021 16:17:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1631809053; bh=c4V6EWY3Wn/cNSs1oKxOGg3WnslcDrOHs2+AwiRU454=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Q1Z2eoc0DJUT/faJI4uRiavZO3Hi4Ty/MmKv+o8VVZVTZ5cP+gcpg8QHoGYxnHCGq SUChXvtCjKfqNJSMG6+Y03DW87UGNA38VMxpdSLSLYrlwhf5tOBh/R7WIFZ+lUneIn qSLGaAzxpQINu7raQIvmEevjRYSL72TlmEcqUkcM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Juergen Gross , Jan Beulich Subject: [PATCH 5.13 014/380] xen: fix setting of max_pfn in shared_info Date: Thu, 16 Sep 2021 17:56:11 +0200 Message-Id: <20210916155804.456268156@linuxfoundation.org> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20210916155803.966362085@linuxfoundation.org> References: <20210916155803.966362085@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Juergen Gross commit 4b511d5bfa74b1926daefd1694205c7f1bcf677f upstream. Xen PV guests are specifying the highest used PFN via the max_pfn field in shared_info. This value is used by the Xen tools when saving or migrating the guest. Unfortunately this field is misnamed, as in reality it is specifying the number of pages (including any memory holes) of the guest, so it is the highest used PFN + 1. Renaming isn't possible, as this is a public Xen hypervisor interface which needs to be kept stable. The kernel will set the value correctly initially at boot time, but when adding more pages (e.g. due to memory hotplug or ballooning) a real PFN number is stored in max_pfn. This is done when expanding the p2m array, and the PFN stored there is even possibly wrong, as it should be the last possible PFN of the just added P2M frame, and not one which led to the P2M expansion. Fix that by setting shared_info->max_pfn to the last possible PFN + 1. Fixes: 98dd166ea3a3c3 ("x86/xen/p2m: hint at the last populated P2M entry") Cc: stable@vger.kernel.org Signed-off-by: Juergen Gross Reviewed-by: Jan Beulich Link: https://lore.kernel.org/r/20210730092622.9973-2-jgross@suse.com Signed-off-by: Juergen Gross Signed-off-by: Greg Kroah-Hartman --- arch/x86/xen/p2m.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/arch/x86/xen/p2m.c +++ b/arch/x86/xen/p2m.c @@ -618,8 +618,8 @@ int xen_alloc_p2m_entry(unsigned long pf } /* Expanded the p2m? */ - if (pfn > xen_p2m_last_pfn) { - xen_p2m_last_pfn = pfn; + if (pfn >= xen_p2m_last_pfn) { + xen_p2m_last_pfn = ALIGN(pfn + 1, P2M_PER_PAGE); HYPERVISOR_shared_info->arch.max_pfn = xen_p2m_last_pfn; }