Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp588179imm; Thu, 31 May 2018 06:06:38 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKMx2eymzxzpIjtZiKqWtKRC9Jgh66vVxfn27bO0umsZrtFdh2LEbsSMtbNCfsFXnuYR/aN X-Received: by 2002:a63:6945:: with SMTP id e66-v6mr5559533pgc.306.1527771998191; Thu, 31 May 2018 06:06:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527771998; cv=none; d=google.com; s=arc-20160816; b=rH+irsV7hJHS9VP7eOoM35YxaBfppkfWfuU1Jkl0ygyO6qdR+nMqRgDUM1fBgyIY90 P2/fvId3P9DOcy14YEwGWbCBX4zxR3Oi8Aek7za5ioO3zZXrsHAQ+VzslSm7aTEzZRAD mVTnOaFHkPAFveYcqu+FDtkaVCtzqjhLw/yb/IVtIPAqIhDGUDXWRx6Q4Mexi8LwT1Hv KSKHfsx7ZhTCm8fVTAcp+e34kD8xEzLizns8PetF2GCDtv+AQvc8yvvpQ/jA5ZdnPZIK 0etKRNyHEM5am2NLSx529QvV+xH+IKu5RRG6+gDlcOwZroWp5VYq/nEAbG0v6k4wUJz0 YEug== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=YgJbyduXta/UoL+48ohq7y/fH4EroMJTGhYXcLucHds=; b=bujx3QJQr3BesiFQIqfPoz9jYNFyxoUt+ynCKvEtHsBootGVTHLNuqygu5PrwR1C+S wQuNWP6VNdRbPHxdpBaAXmc6X1FNLwSPFxm6o2mcxli8/c7DjKfCUWWfns4kK6gHzfhk ExdAtyinUW2OCwGSwdCveAFEAkOk87s6RZzkwN2sFptLJwGNfogs/z1+/YT7h8kfwO/H MoadEvxHCenzm9fJ2TKJw7IRADu6GALef33vq0MRZFiPGmwZnpc1yssxcT0p65ZeDgLZ qHDu7fpviGq0tgPP317Rg3c/pgsAG15q6Yc+rjiVujrubJAevjbEJ/aNm6v6TQHS63RF XoyQ== ARC-Authentication-Results: i=1; mx.google.com; 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 m13-v6si29448186pgu.237.2018.05.31.06.06.24; Thu, 31 May 2018 06:06:38 -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; 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 S1755199AbeEaNEi (ORCPT + 99 others); Thu, 31 May 2018 09:04:38 -0400 Received: from foss.arm.com ([217.140.101.70]:41198 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755025AbeEaNEh (ORCPT ); Thu, 31 May 2018 09:04:37 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id D0B8E15AD; Thu, 31 May 2018 06:04:36 -0700 (PDT) Received: from [10.1.210.88] (e110467-lin.cambridge.arm.com [10.1.210.88]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 83DBA3F53D; Thu, 31 May 2018 06:04:34 -0700 (PDT) Subject: Re: [PATCH 4/7] iommu/amd: make sure TLB to be flushed before IOVA freed To: Zhen Lei , Will Deacon , Matthias Brugger , Rob Clark , Joerg Roedel , linux-mediatek , linux-arm-msm , linux-arm-kernel , iommu , linux-kernel Cc: Hanjun Guo , Libin , Guozhu Li , Xinwei Hu References: <1527752569-18020-1-git-send-email-thunder.leizhen@huawei.com> <1527752569-18020-5-git-send-email-thunder.leizhen@huawei.com> From: Robin Murphy Message-ID: Date: Thu, 31 May 2018 14:04:32 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1527752569-18020-5-git-send-email-thunder.leizhen@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 31/05/18 08:42, Zhen Lei wrote: > Although the mapping has already been removed in the page table, it maybe > still exist in TLB. Suppose the freed IOVAs is reused by others before the > flush operation completed, the new user can not correctly access to its > meomory. This change seems reasonable in isolation, but why is it right in the middle of a series which has nothing to do with x86? Robin. > Signed-off-by: Zhen Lei > --- > drivers/iommu/amd_iommu.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c > index 8fb8c73..93aa389 100644 > --- a/drivers/iommu/amd_iommu.c > +++ b/drivers/iommu/amd_iommu.c > @@ -2402,9 +2402,9 @@ static void __unmap_single(struct dma_ops_domain *dma_dom, > } > > if (amd_iommu_unmap_flush) { > - dma_ops_free_iova(dma_dom, dma_addr, pages); > domain_flush_tlb(&dma_dom->domain); > domain_flush_complete(&dma_dom->domain); > + dma_ops_free_iova(dma_dom, dma_addr, pages); > } else { > pages = __roundup_pow_of_two(pages); > queue_iova(&dma_dom->iovad, dma_addr >> PAGE_SHIFT, pages, 0); >