Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp435337yba; Wed, 15 May 2019 04:04:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqzTPhknfvftV9kdaQ/YowVCsSfRv35pyIpV3BgYLagCOXwNBpB6VqNo6xtcrF0z5pYAo63L X-Received: by 2002:a63:5322:: with SMTP id h34mr43735529pgb.413.1557918256674; Wed, 15 May 2019 04:04:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557918256; cv=none; d=google.com; s=arc-20160816; b=p8sBN4MpdecUPherAlNbgBwZgYssTSNAQHp3M20uYaoHp5q50ZTKwyDwRhgm3MLZFo NFywaQUxiW531QajXK5+A+SRz+zibUtgNngHPNYff2KDOAC1+ZLHZtUk9VVh4R+tk5tS JksaVjF4Art1jstxLq6la4Qj7YuxsdC7GMRDrs01BIuM/0rphQ0ji2l/ZRgeKexOY8Cw DQffRou3sQdyO05FPVJd9b5HGRmtmihMLt+tuZ5S3TmhjKomnCtmdWIdIrquDhyoLkSY 7roDf89v7XdZt8c5v2wCNEHnQ37cp8U8bnUKKNa5swrs9PSyLM0j1tQmn2qfUqsRDDL6 hhog== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=GT/dXfomeY40vhSA0ucEuxz/Ivp6J0vDYSl0aYaVqns=; b=p3eq0En0GwHTtD9eLI2xUDFsykwHq3vc9+RsbmUvYVjd6UCYd0xlV2qih9tPdi33fr aoUKZ3LNM0XJ495oKLpri2IgHcDJCEJtSZvYh555BSfXNma/Pac5cqyEmSOgnv5ZwOFi 4r40V6nW7uIWW1uCuuUC0m39fZDtvtgmw9LtPYJjWkZHoDSZtuvzbt1hhi0/lBziaF24 XpVqq5T4mkmLtmrJjy9flC3fiLqPMfAMAy9DqknnY9Bh9PKto+zss30Dj26JKaJI4XN6 ymmUudgt5n5lro5c6EQQrkdOYeDlkG0jCHFyZ3aSmzZttw2FVV+QfeRST4RxoUwy6NOA xhFQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=1AogZBld; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c20si1824193pfn.256.2019.05.15.04.03.53; Wed, 15 May 2019 04:04:16 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=1AogZBld; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727776AbfEOLBs (ORCPT + 99 others); Wed, 15 May 2019 07:01:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:58848 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727265AbfEOLBp (ORCPT ); Wed, 15 May 2019 07:01:45 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C899C216FD; Wed, 15 May 2019 11:01:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1557918105; bh=e7y/WSro2eF3J9GEEv3f0dnT2fkMcdnBHSY38CIXJ9Y=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=1AogZBldDfc2RLF5DHNOvf+18h3QLJxu5It27OSoS8hNbMLeiN9GKyIisuDEf/kHZ Z57X94bnlH6EMoxzfUutd+2+4n4CbfFTrmP8jiTLwZUIXUqfqg2PyY5F/v5GccFG6X gAFE9o+Im9iuOgUfzSygWcNzNj33fV3VSpIqFa8w= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Joerg Roedel , Sasha Levin Subject: [PATCH 3.18 57/86] iommu/amd: Set exclusion range correctly Date: Wed, 15 May 2019 12:55:34 +0200 Message-Id: <20190515090653.790224124@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190515090642.339346723@linuxfoundation.org> References: <20190515090642.339346723@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [ Upstream commit 3c677d206210f53a4be972211066c0f1cd47fe12 ] The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons. So correctly set the exclusion range in the hardware to the last page which is _in_ the range. Fixes: b2026aa2dce44 ('x86, AMD IOMMU: add functions for programming IOMMU MMIO space') Signed-off-by: Joerg Roedel Signed-off-by: Sasha Levin --- drivers/iommu/amd_iommu_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/amd_iommu_init.c index 2f3475247f0ff..127f9cc563e9b 100644 --- a/drivers/iommu/amd_iommu_init.c +++ b/drivers/iommu/amd_iommu_init.c @@ -294,7 +294,7 @@ static void iommu_write_l2(struct amd_iommu *iommu, u8 address, u32 val) static void iommu_set_exclusion_range(struct amd_iommu *iommu) { u64 start = iommu->exclusion_start & PAGE_MASK; - u64 limit = (start + iommu->exclusion_length) & PAGE_MASK; + u64 limit = (start + iommu->exclusion_length - 1) & PAGE_MASK; u64 entry; if (!iommu->exclusion_start) -- 2.20.1