Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4738141pxj; Wed, 12 May 2021 12:05:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz7PkP8j3nBgVAdAyF17PFSV3/i/seyTqwJLkUZcZ0/bl69ZqkccgBMrl6T76RO6s/G66x3 X-Received: by 2002:a17:906:e251:: with SMTP id gq17mr16011087ejb.89.1620846222583; Wed, 12 May 2021 12:03:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620846222; cv=none; d=google.com; s=arc-20160816; b=gvkriCV6SYhyQFpSSV6uP/JVVe5SrAtQm9qP2QyfznrqtNX0oue0W3rhGje8MmvGKI oRwrzFfgWhuSD3aFRzJK28aoebMww3aEmUTESLvm8W15obUiSg0HE4dfvaDFmu+GXlek TgaIg5YAtvDjIJabXwLV8D448FlGdFVSK82sXqpJKDBOSRmbAEy44rTSpMpzi8tnuGDc whHoNIi2UrHtFm4EOTbcZr+uUaLHHbMcedzzIK9qUOiirAQolZFdFhPuimhQaXCzIaNN DHQGE1XtbxD12CwZAXj6MJaAKBSL36pXGnlmH1dGtpNes8tvnapaR6BNVfJUnDnJKi6Z XAYw== 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=OVIat1jNJ/Hx2V+nPc6ck3J9pN/Sts7gF77NUUqn0fY=; b=nSMKPDNzoCL6DMqv5YCW5+6DvQA3/YMNORu2kw7vJ2i4HXLPs6EoBKJBD/OfxTR9G2 eOEPzSlmYFaWLovnWCLoTjvvbmgsyXgZWUh7IeCmwZYO+y9i9wBkJ0NSwRmGnltIvWfn hYFldNXfNWGw0XBKl7MNu0tu/h8Yn7utpWhlYozN8HqGO4IWSgyv54/x82sfC3LYw/a5 CuFoI/lW7ifVQo1bUErzOjdAn3j8UmnEqNL0TG8lnlw0F+mybeJ2/jWTPHav0O04M1vw YjvTtTo8/OgZKYOaIESLfYxBIa6m++WW8QXaGTVjzocEAuZHz48XWY8pdCo9l2CniP5N XdvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=bbdLmH1H; 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 g16si761669ejm.224.2021.05.12.12.03.11; Wed, 12 May 2021 12:03:42 -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=bbdLmH1H; 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 S1376910AbhELS4D (ORCPT + 99 others); Wed, 12 May 2021 14:56:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:33484 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244205AbhELQmm (ORCPT ); Wed, 12 May 2021 12:42:42 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 59AA361D25; Wed, 12 May 2021 16:11:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1620835902; bh=YudxFErCNGEG/IMcM55fzLDfeqLIl64lIT/PgvE9NZE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=bbdLmH1HFD/y8qolWmEvgJsHPz/WbQClEEshJ2zG3xlB1ZfJzyd4HVlZGnx70BCVt 3UEarOs0qAznAv2nKWEe0pRl6778XabqaOzAH5S882UpxOoUv44CNCeaO5zcs38d97 BfCxlqQYbD2dOIzliVygPQWGrmGYrmLHFXYUzgjw= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Ashok Raj , Lu Baolu , Joerg Roedel , Sasha Levin Subject: [PATCH 5.12 495/677] iommu/vt-d: Remove WO permissions on second-level paging entries Date: Wed, 12 May 2021 16:49:01 +0200 Message-Id: <20210512144853.828509274@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210512144837.204217980@linuxfoundation.org> References: <20210512144837.204217980@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: Lu Baolu [ Upstream commit eea53c5816889ee8b64544fa2e9311a81184ff9c ] When the first level page table is used for IOVA translation, it only supports Read-Only and Read-Write permissions. The Write-Only permission is not supported as the PRESENT bit (implying Read permission) should always set. When using second level, we still give separate permissions that allows WriteOnly which seems inconsistent and awkward. We want to have consistent behavior. After moving to 1st level, we don't want things to work sometimes, and break if we use 2nd level for the same mappings. Hence remove this configuration. Suggested-by: Ashok Raj Fixes: b802d070a52a1 ("iommu/vt-d: Use iova over first level") Signed-off-by: Lu Baolu Link: https://lore.kernel.org/r/20210320025415.641201-3-baolu.lu@linux.intel.com Signed-off-by: Joerg Roedel Signed-off-by: Sasha Levin --- drivers/iommu/intel/iommu.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c index b5d3301b2700..36d60536ae8d 100644 --- a/drivers/iommu/intel/iommu.c +++ b/drivers/iommu/intel/iommu.c @@ -2346,8 +2346,9 @@ __domain_mapping(struct dmar_domain *domain, unsigned long iov_pfn, return -EINVAL; attr = prot & (DMA_PTE_READ | DMA_PTE_WRITE | DMA_PTE_SNP); + attr |= DMA_FL_PTE_PRESENT; if (domain_use_first_level(domain)) { - attr |= DMA_FL_PTE_PRESENT | DMA_FL_PTE_XD | DMA_FL_PTE_US; + attr |= DMA_FL_PTE_XD | DMA_FL_PTE_US; if (domain->domain.type == IOMMU_DOMAIN_DMA) { attr |= DMA_FL_PTE_ACCESS; -- 2.30.2