From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 892F2C433DF for ; Tue, 9 Jun 2020 05:57:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4864B20814 for ; Tue, 9 Jun 2020 05:57:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1591682227; bh=l6ipBhA5f8rK4KSDgULx6FzzquE+2+fxxHeCVYrSBu0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Hnqxd1d/kicf8tVWMBuJMbsWLdArxpbV7nwFEC4my6WdalisPLaT5ZiFyglNKRtnB nhiuLwjBcNYsT1H3TufnB4iB1jHEuCL14xNOtNBCe/Nwsd8bf+maozHaUxjQXpj/yP VJ5juk7cr6q1W8AN5jAmKXE3Gr88vsXXCtNHEepc= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727883AbgFIF5F (ORCPT ); Tue, 9 Jun 2020 01:57:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:38504 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727122AbgFIF5F (ORCPT ); Tue, 9 Jun 2020 01:57:05 -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 1CD37207F9; Tue, 9 Jun 2020 05:57:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1591682224; bh=l6ipBhA5f8rK4KSDgULx6FzzquE+2+fxxHeCVYrSBu0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=M9adgHhT8SWWIYkFtoCSNXvqZzHrk6SOVJQiT5pfWbSeJKYwmIC8A5rT7OdSYT2vn KIddEWjzGL4Vaf8Jfr7QXltgcPIJo2amSuloXTLkzl8pJWdQGaA5AQp4E59UdZk9mF bFBpt50gWgbwlk6F2AqEaCxz6sw45MgXj7p40Afc= Date: Tue, 9 Jun 2020 07:57:02 +0200 From: Greg Kroah-Hartman To: Jesse Barnes Cc: Rajat Jain , Rajat Jain , Bjorn Helgaas , "Raj, Ashok" , "Krishnakumar, Lalithambika" , Bjorn Helgaas , linux-pci , Mika Westerberg , Jean-Philippe Brucker , Prashant Malani , Benson Leung , Todd Broch , Alex Levin , Mattias Nissler , Zubin Mithra , Bernie Keany , Aaron Durbin , Diego Rivas , Duncan Laurie , Furquan Shaikh , Christian Kellner , Alex Williamson , Joerg Roedel , Linux Kernel Mailing List Subject: Re: [RFC] Restrict the untrusted devices, to bind to only a set of "whitelisted" drivers Message-ID: <20200609055702.GB497287@kroah.com> References: <20200603060751.GA465970@kroah.com> <20200603121613.GA1488883@kroah.com> <20200605080229.GC2209311@kroah.com> <20200607113632.GA49147@kroah.com> <20200608175015.GA457685@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Mon, Jun 08, 2020 at 11:29:58AM -0700, Jesse Barnes wrote: > > Now, as to you all getting some sort of "Hardware flag" to determine > > "inside" vs. "outside" devices, hah, good luck! It took us a long time > > to get that for USB, and even then, BIOSes lie and get it wrong all the > > time. So you will have to also deal with that in some way, for your > > userspace policy. > > I think that's inherently platform specific to some extent. We can do > it with our coreboot based firmware, but there's no guarantee other > vendors will adopt the same approach. But I think at least for the > ChromeOS ecosystem we can come up with something that'll work, and > allow us to dtrt in userspace wrt driver binding. Why not work with the UEFI group to add this to their spec so that it will work for all future firmware releases, not just your vendor-specific one? :) thanks, greg k-h