mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Derrick <jonathan.derrick@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Arjan van de Ven <arjan@linux.intel.com>,
	Alan Cox <alan@linux.intel.com>,
	Dan J Williams <dan.j.williams@intel.com>
Subject: Re: [RFC 2/3] module: Ignore delete_id parameter
Date: Thu, 28 Sep 2017 09:57:02 -0600	[thread overview]
Message-ID: <c9b6b6d0-27bb-1d37-da34-06ecc714bbc4@intel.com> (raw)
In-Reply-To: <20170928090234.GB12599@kroah.com>

On 09/28/2017 03:02 AM, Greg Kroah-Hartman wrote:
> On Wed, Sep 27, 2017 at 04:40:21PM -0400, Jon Derrick wrote:
>> The PCI driver delete_id parameter is handled in each individual driver
>> registration callback.
>>
>> Signed-off-by: Jon Derrick <jonathan.derrick@intel.com>
>> ---
>>  kernel/module.c | 7 +++++++
>>  1 file changed, 7 insertions(+)
>>
>> diff --git a/kernel/module.c b/kernel/module.c
>> index de66ec8..2b2dccf 100644
>> --- a/kernel/module.c
>> +++ b/kernel/module.c
>> @@ -3620,6 +3620,13 @@ static int unknown_module_param_cb(char *param, char *val, const char *modname,
>>  		return 0;
>>  	}
>>  
>> +	/*
>> +	 * Ignore driver delete list arguments. They are handled by driver
>> +	 * registration callbacks
>> +	 */
>> +	if (strcmp(param, "delete_id") == 0)
>> +		return 0;
> 
> Why?  This is only for the PCI core as you have defined it in this
> patchset, but you just broke this module id for all other kernel modules
> in the system :(
> 
> If you want to do this, you need to provide this feature for _all_
> kernel drivers...
> 
> thanks,
> 
> greg k-h
> 
Yes I'm not particularly happy about this one either. I will make this
more robust if the blacklisting idea is sound.

  reply	other threads:[~2017-09-28 15:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 20:40 [RFC 0/3] Introduce PCI device blacklisting Jon Derrick
2017-09-27 20:40 ` [RFC 1/3] PCI: pci-driver: Introduce pci device delete list Jon Derrick
2017-09-28  9:09   ` Greg Kroah-Hartman
2017-09-28 15:53     ` Jon Derrick
2017-09-28 15:58     ` Dan Williams
2017-09-27 20:40 ` [RFC 2/3] module: Ignore delete_id parameter Jon Derrick
2017-09-28  6:03   ` Dan Williams
2017-09-28 15:57     ` Jon Derrick
2017-09-28  9:02   ` Greg Kroah-Hartman
2017-09-28 15:57     ` Jon Derrick [this message]
2017-09-27 20:40 ` [RFC 3/3] Documentation: Add pci device delete_id interface Jon Derrick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c9b6b6d0-27bb-1d37-da34-06ecc714bbc4@intel.com \
    --to=jonathan.derrick@intel.com \
    --cc=alan@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome