Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp382908pxt; Thu, 5 Aug 2021 01:59:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzorjFuOHhF28B3k6bOPNzqhnoI6Hy8geEPSs+QPqIzJ+Tpc/Av+6US/DG1jv2FDvCPYTAL X-Received: by 2002:aa7:c68e:: with SMTP id n14mr5207374edq.66.1628153981651; Thu, 05 Aug 2021 01:59:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628153981; cv=none; d=google.com; s=arc-20160816; b=vpIiLVCpeJsJemLl9ndpqAOjkAIIJmf8f5sIoltbA3NxvV2tpbpSkHS4WOKkqLfNSz 8PUOkGQciBu2aIzvXc14a8D/U9HSG4D0XzAIU0k7WORk6XvjOagNemaLDZYDvPSbFL3m uv0gRtGI1Fqg0LwDv4Ddo9BfOaVoKpF3RP0U+zdK7KI2shIcfnQKc5HL4amK4F9revrz SBZdxqjLPUZH3pTbb+0nSvcKaiLw94jB68y2UDFOYeJGY4yM0npLjQbtFaYPlhvB7udr cF4KcJKYHI97Oa4RmsMvSIRwdGJxolgMuohLYYpZ18l8XyIAW5dBZSQkY63dAZhaUAiO iRLg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=EjOBbJuIBPG+J1KErAZ58sCUbi3RLZ0DSdDXOxLPsno=; b=rDS50qPZn8/3Cc2pAw+StE6MzBMZ0Wsj1rNF3PqFbsGNzUom5js7+NO0IvdGVbnQRW bglarc4dadKs7HjSjDzPFc+jvjAmaX1NUgPyuEaa1/Tun+fvJArIxffcdLZfx3+rf6RS oAs4+6AcPM7zySLtmxzNdNrVUK2pztVOrnCje/w4SlSd5bXR63Sm+b/8CGXDqb/4zH0c 5dg+kcDaj0f31h4NkNrVcEITch95xukwHmSDI1YuV8G3QkPgnYHwdkMjizrsuFTQqxzb OJoKMjJblo4Q0auLM+aMJGNMQUa6Qs+Cpugy1BanTAaOvfJRVpiO5f3nnMzUT38y46XC Smmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=rFlJUwWJ; 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 gn9si4781678ejc.136.2021.08.05.01.59.18; Thu, 05 Aug 2021 01:59:41 -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=rFlJUwWJ; 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 S238981AbhHEHzv (ORCPT + 99 others); Thu, 5 Aug 2021 03:55:51 -0400 Received: from mail.kernel.org ([198.145.29.99]:60082 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236977AbhHEHzt (ORCPT ); Thu, 5 Aug 2021 03:55:49 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 4CC7960E53; Thu, 5 Aug 2021 07:55:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1628150135; bh=QiUEnspHIRAkgxLeABfnYxzZnyZRQryISrYTf838FMo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=rFlJUwWJjk7fcKpYFUKLhCEA/XiYbg0JljwDzq67OGE9H3W2IkoQtLCt4zRTXhybt wEcbwPx1g+Ph0NZI5vYVPSmtA6v2cDUkVpgxi2potOwMQJ/oVA6BzZWEs6uaqY0BFy P31xflsMYQ0/65lBdZzR9KkwzFn0c1uAoUiH8Jck= Date: Thu, 5 Aug 2021 09:55:33 +0200 From: Greg Kroah-Hartman To: Andi Kleen Cc: Kuppuswamy Sathyanarayanan , "Rafael J . Wysocki" , Jonathan Corbet , Dan Williams , Kuppuswamy Sathyanarayanan , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH v1] driver: base: Add driver filter support Message-ID: References: <20210804174322.2898409-1-sathyanarayanan.kuppuswamy@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 05, 2021 at 09:49:29AM +0200, Greg Kroah-Hartman wrote: > On Wed, Aug 04, 2021 at 12:50:24PM -0700, Andi Kleen wrote: > > > And what's wrong with the current method of removing drivers from > > > devices that you do not want them to be bound to? We offer that support > > > for all busses now that want to do it, what driver types are you needing > > > to "control" here that does not take advantage of the existing > > > infrastructure that we currently have for this type of thing? > > > > I'm not sure what mechanism you're referring to here, but in general don't > > want the drivers to initialize at all because they might get exploited in > > any code that they execute. > > That is exactly the mechanism we have today in the kernel for all busses > if they wish to take advantage of it. We have had this for all USB > drivers for well over a decade now, this is not a new feature. Please > use that instead. Hm, wait, maybe that didn't get merged yet, let me dig...