Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933446Ab3GCVhL (ORCPT ); Wed, 3 Jul 2013 17:37:11 -0400 Received: from mail-vb0-f42.google.com ([209.85.212.42]:56043 "EHLO mail-vb0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933279Ab3GCVhJ (ORCPT ); Wed, 3 Jul 2013 17:37:09 -0400 MIME-Version: 1.0 In-Reply-To: References: <87ehfhtftn.fsf@rustcorp.com.au> <87sj3tsawh.fsf@rustcorp.com.au> <87hak8qfu5.fsf@rustcorp.com.au> <87sj3qpwdz.fsf@rustcorp.com.au> <87a9m6sri3.fsf@rustcorp.com.au> <9F26321B-7088-4D16-80D5-72EB388F8E49@redhat.com> <51D491AD.7050008@suse.cz> <51D49655.8030206@suse.cz> From: Andy Lutomirski Date: Wed, 3 Jul 2013 14:36:48 -0700 Message-ID: Subject: Re: [RFC PATCH] Allow optional module parameters To: Lucas De Marchi Cc: Michal Marek , Jonathan Masters , Rusty Russell , "linux-kernel@vger.kernel.org" , Ben Hutchings , "linux-kbuild@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1703 Lines: 44 On Wed, Jul 3, 2013 at 2:31 PM, Lucas De Marchi wrote: > On Wed, Jul 3, 2013 at 6:23 PM, Michal Marek wrote: >> Dne 3.7.2013 23:17, Andy Lutomirski napsal(a): >>> On Wed, Jul 3, 2013 at 2:03 PM, Michal Marek wrote: >>>> Dne 1.7.2013 18:33, Jonathan Masters napsal(a): >>>>> One caveat. Sometimes we have manufactured parameters intentionally >>>>> to cause a module to fail. We should standardize that piece. >>>> >>>> You have: >>>> >>>> blacklist foo >>>> >>>> to prevent udev from loading a module and >>>> >>>> install foo /bin/true >>>> >>>> to prevent modprobe from loading the module at all. What is the >>>> motivation for inventing a third way, through adding invalid parameters? >>>> >>> >>> FWIW, I've occasionally booted with modulename.garbage=1 to prevent >>> modulename from loading at boot. It may be worth adding a more >>> intentional way to do that. >> >> Hm, right, there seems to be no clean way to achieve this via a >> commandline argument. Maybe define a magic module option to tell the >> module loader not to load a module? > > modprobe.blacklist=modname1,modname2,... is already there, though all > the silliness of blacklist applies unless "-b" is passed (that's the > equivalent behavior of udev) That would probably be good enough for me. It would be neat if this worked for built-in "modules" as well, but that would probably be quite intrusive. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/