Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp4672486img; Tue, 26 Mar 2019 14:19:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqyM3lwHwp5vlhN1aheXZw5rEkmot017Mx7/BpZTL3kP/S2jmRr07hhM+ImbMqLZKwJyJpiX X-Received: by 2002:aa7:8ad4:: with SMTP id b20mr24858457pfd.249.1553635195190; Tue, 26 Mar 2019 14:19:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553635195; cv=none; d=google.com; s=arc-20160816; b=xjD/80nGnodWxgr8dLEZ9xXYwyK8/z1fdx5Xsb5aO3J5ScTGrnQ10cWN3+7OPXwrQZ ypzeFq72tpVKpW3BGxFzl1obUyYNIqewbz46oiwW3bB3Mj+MxsQmMAKQKIK5bDGcvLYZ 0wKcLxogSJ/b9npXzQVO29J91DrkUZL8LDIXLtYioliISikfJLvSrs94k/+GwKwMNPtX ChGZrpChcBgQIJngvIfTm8IVYODfTFuEjzE5dL6B7JDJPBZYCn1mksqVBlebW1lP6Q1u EFBZ8SajcG9UM288iYkfv9bgJSxFH46HNfIwbezMOPKEbUKI0k0/MzGgG9hY/0NRijJG I16A== 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 :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=JBXd8iktQ6+aVhAfWjY0gg9wTJ851VadgD3dnMkDofc=; b=nGISwyRjgDB84vQfGhb39MvFf8tcODNmvz1CJxXL7V0tW9BVad+A77xw3hjnTqQcxt cZSrYwxUqwfMlHlbVL0KCNI0N/mmXu1w36sKeOLVQj3cTo18KAZEzaNXa80oBx/KG1yV jcijsFt4ZVMXYp2R8PIU1axtxCLHnDna/qpang/cagAJrEQLtVmAOFDjuhA7xFlhrsKB 6M6rgUE1zjHn5byxw3govv1bMCB3CKHjWFZ68J0ofGfWyPS6ZQyIgjUB/3dsRSjjfSIe yMk/WtfpnZ2TiYkjBLSrMpxAkcTOqlDbLkehhP3nxDzTuNMH4ByHyplxW90OJfAFEphR JKSQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e2si16846748pgs.387.2019.03.26.14.19.39; Tue, 26 Mar 2019 14:19:55 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731994AbfCZVTG (ORCPT + 99 others); Tue, 26 Mar 2019 17:19:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58864 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727145AbfCZVTF (ORCPT ); Tue, 26 Mar 2019 17:19:05 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 67F66E6A6F; Tue, 26 Mar 2019 21:19:05 +0000 (UTC) Received: from x1.home (ovpn-116-99.phx2.redhat.com [10.3.116.99]) by smtp.corp.redhat.com (Postfix) with ESMTP id 9D9DC1001E84; Tue, 26 Mar 2019 21:19:03 +0000 (UTC) Date: Tue, 26 Mar 2019 15:19:03 -0600 From: Alex Williamson To: Andy Lutomirski Cc: Matthew Garrett , James Morris , LSM List , LKML , David Howells , Linux API , Matthew Garrett , Matthew Garrett , Bjorn Helgaas , linux-pci@vger.kernel.org Subject: Re: [PATCH V31 10/25] PCI: Lock down BAR access when the kernel is locked down Message-ID: <20190326151903.257724d5@x1.home> In-Reply-To: References: <20190326182742.16950-1-matthewgarrett@google.com> <20190326182742.16950-11-matthewgarrett@google.com> Organization: Red Hat MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 26 Mar 2019 21:19:05 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 26 Mar 2019 13:55:39 -0700 Andy Lutomirski wrote: > On Tue, Mar 26, 2019 at 11:28 AM Matthew Garrett > wrote: > > > > From: Matthew Garrett > > > > Any hardware that can potentially generate DMA has to be locked down in > > order to avoid it being possible for an attacker to modify kernel code, > > allowing them to circumvent disabled module loading or module signing. > > Default to paranoid - in future we can potentially relax this for > > sufficiently IOMMU-isolated devices. > > Does this break vfio? No, vfio provides its own interface to pci config space. Thanks, Alex