Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp2319499pxb; Mon, 20 Sep 2021 18:42:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxGJbg18FETchamORaEMOwZgJw2Z6YUByJfhTyhHO1z88ioLCu0VKIc/uLFvDLijOEbtjQR X-Received: by 2002:a05:6602:2182:: with SMTP id b2mr5530899iob.45.1632188559086; Mon, 20 Sep 2021 18:42:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632188559; cv=none; d=google.com; s=arc-20160816; b=RAYGp5p20fb572WlcY8wCbEixuvUI+vv2ras5bKWK5JJAJCDhNCbBATCSJt5bXIC+p Y0PDCoPRTdUl5tOR5tXUGGFO8jPI+gFkwUS6hFTMDk1MDIQSGuUsQMqv8i1BTab1Aacq FJjzsmhupXbs6LzSGiph5wlAwkXG+tAxKCanbIY9TdIaXGPhoXOR4gYNle4XWVOFeInd dBetyGVnX03IAUW8s0R6H6vZrm2T/N2OdV3/KHk8nmQ5XuVh5nW7PM/wQkeN0Wftj5Dk HILHVFnoE1WkOrvelaIO1PK2cIivfDdhmGZON+I7PiZOoN1dY7QvnUS0k/7SVwCYGNzM YueQ== 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=XuP29aSC32jLQ1Z4o0s1lv14C6+HpfhrKtydddo2fws=; b=IJuCO2QLB0Be9Z5DtWU8FI+6L3QDlkVwgLAX0FhBUxM/4iRZw+qDdNUwpeDasobwI/ Rh9iHOWJJ5lqCa9eNt2vmogNgWPjtAEfl3K40gr72qrL6NHJo5xlI10iS+RxnxiCaFvf r06s57cZLJu9E6iiQQTNkILUuPZBD3CaCZ5IVcS1zigLT+kHzS4Hl4BuwstTlrbjqYlA eYuMxH14VTeIQbOw3aPpuA2+t4VMkB0HYVI4FT8thPacvjSiiF/5/hYR0Jokmdw/NYL2 WFQAN1tNawrbTT4P0td6F6kZk17ZtNJ192fBEnUBfC+gXWFNB7NYM7PxApi9mmDrJx3u TPhQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=g57UynP5; 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 v3si13265021jao.112.2021.09.20.18.42.28; Mon, 20 Sep 2021 18:42: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=g57UynP5; 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 S243328AbhITQus (ORCPT + 99 others); Mon, 20 Sep 2021 12:50:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:37262 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230132AbhITQtT (ORCPT ); Mon, 20 Sep 2021 12:49:19 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 3280C61262; Mon, 20 Sep 2021 16:47:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1632156469; bh=R5RubUIDV5mJf/Ntg1nlkaygmNTmSRGtpF4N1JRkJbs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=g57UynP5mKg5GZUCeZCWn8PATzX7r/35v7UsPvD55DPwfSmaEg1FKQvfo4hKcyMjo uG4W20ulDfNuE0IObrag2I0iokff3EKhVDIrvjcRrXAQob5TFd2r5D3Vr3OCdxctGZ o0JBe70tiGQTrzAWIoLm5uqJkDg3cMi6V2Dzgr40= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Juergen Gross , Jan Beulich Subject: [PATCH 4.4 074/133] xen: fix setting of max_pfn in shared_info Date: Mon, 20 Sep 2021 18:42:32 +0200 Message-Id: <20210920163915.067760490@linuxfoundation.org> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20210920163912.603434365@linuxfoundation.org> References: <20210920163912.603434365@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 @@ -623,8 +623,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; }