Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp1553169ybg; Tue, 2 Jun 2020 13:11:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJztMRWPT942+QOVRd/rSfayQcyMRjRx5tMsHDQCynT6qwL9+ojTpEav2CYKPRnE+MvUCcvs X-Received: by 2002:aa7:cb4a:: with SMTP id w10mr15985165edt.46.1591128668460; Tue, 02 Jun 2020 13:11:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591128668; cv=none; d=google.com; s=arc-20160816; b=jvodXgr//3MR8dTdQQR6fPS6e0Op1Sn3nzlYLBWWMutGtY/dY4yyTQbYdmfsU1l5Gk eLnf2szp0j+z5PHdZRJxJbjLfrTYjCF5T5cbTinoIrzrmi9vhp7b/N1SdyRP662nXkkJ +vNujFnKtzigfIB/Zh8HniYIADD0jV76GI1wECxQueDfuN5kNmlKwBl4HDuqZw/QUAHP Cc9jbHEo78sitqbMJJGqtBG7ElCqcMB1DEARFQmgNmUv533/WS342qeFOF72FIgfHUej zgnt8eAcnDiTflF/vP93YeSS3+qXf2roZf3y7p54YULNmhJVtODPJFjDhJi4WMshEj97 nqYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:ironport-sdr:ironport-sdr; bh=FqX1933P2ZjjCFI9oqoUyYNPW05UCcHa2TJVLVmpLI0=; b=qj2GguTllFY8PT4FVD86Y2Qv1OBMfuD1fUDMsuQXe9wmLaTsS4iiHKRGhQDkFVV8Cn QAnU5Y1UEcgzlDvVHeBPy+g3l1epf8mdIC4NFY2l5jxADsV6MWaFUHomOrET1m5p4mLK LIXOlNhmsPl0/KggNnDXyvGAD2322fb5NxeYEtlFrSUSGsddkGUhJVcptuB7cRKx4lJf 6TR4UIP+v/i7+fkpKrEHZ0U71gbVZaIaRnBq+RQ3SODVtC1YXKTJRT1v77xgrveXMY7V YcByJpe5OUEtMm85ogcMgCOoMNuhb/4XAsWogVX9/90eByL7XmrcrQGIV66UKwnhwICU jLTQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e11si1969596ejh.44.2020.06.02.13.10.43; Tue, 02 Jun 2020 13:11:08 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728331AbgFBUFg (ORCPT + 99 others); Tue, 2 Jun 2020 16:05:36 -0400 Received: from mga04.intel.com ([192.55.52.120]:28467 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726139AbgFBUFg (ORCPT ); Tue, 2 Jun 2020 16:05:36 -0400 IronPort-SDR: KzILVJWxaOkFgTBhuJKzfIIlGYk8j96zA4lQqQkjU/Mr8wEpgdImR2tkrZrclyn0SxmGOvzjEC Tq3ozTuQIO2g== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Jun 2020 13:05:35 -0700 IronPort-SDR: j+uz9EZpXx3Aq/tV6t8Xv3otI9hzrOUqAVrLgz40kePv1smgfrIh2DXHXSvd6Y1uDTPIN4kz1l ro0C9uuMJkGQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,465,1583222400"; d="scan'208";a="257227532" Received: from otc-nc-03.jf.intel.com (HELO otc-nc-03) ([10.54.39.25]) by fmsmga007.fm.intel.com with ESMTP; 02 Jun 2020 13:05:35 -0700 Date: Tue, 2 Jun 2020 13:05:35 -0700 From: "Raj, Ashok" To: Rajat Jain Cc: David Woodhouse , Lu Baolu , Joerg Roedel , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Mika Westerberg , lalithambika.krishnakumar@intel.com, rajatxjain@gmail.com, pmalani@google.com, bleung@google.com, levinale@google.com, zsm@google.com, mnissler@google.com, tbroch@google.com, Ashok Raj Subject: Re: [PATCH v2] iommu/vt-d: Don't apply gfx quirks to untrusted devices Message-ID: <20200602200534.GA17363@otc-nc-03> References: <20200602184133.75525-1-rajatja@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200602184133.75525-1-rajatja@google.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rajat On Tue, Jun 02, 2020 at 11:41:33AM -0700, Rajat Jain wrote: > Currently, an external malicious PCI device can masquerade the VID:PID > of faulty gfx devices, and thus apply iommu quirks to effectively > disable the IOMMU restrictions for itself. > > Thus we need to ensure that the device we are applying quirks to, is > indeed an internal trusted device. > > Signed-off-by: Rajat Jain > Acked-by: Lu Baolu > --- > V2: - Change the warning print strings. > - Add Lu Baolu's acknowledgement. > > drivers/iommu/intel-iommu.c | 38 +++++++++++++++++++++++++++++++++++++ > 1 file changed, 38 insertions(+) > > diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c > index ef0a5246700e5..fdfbea4ff8cb3 100644 > --- a/drivers/iommu/intel-iommu.c > +++ b/drivers/iommu/intel-iommu.c > @@ -6214,6 +6214,13 @@ const struct iommu_ops intel_iommu_ops = { > > static void quirk_iommu_igfx(struct pci_dev *dev) > { > + if (dev->untrusted) { > + pci_warn(dev, > + "Skipping IOMMU quirk %s() for potentially untrusted device\n", > + __func__); > + return; > + } > + This check and code seems to be happening several times. Maybe add a simple function to do the test and use in all places? Cheers, Ashok