From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cantor2.suse.de ([195.135.220.15]:51035 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933240Ab3GCVXk (ORCPT ); Wed, 3 Jul 2013 17:23:40 -0400 Message-ID: <51D49655.8030206@suse.cz> Date: Wed, 03 Jul 2013 23:23:33 +0200 From: Michal Marek MIME-Version: 1.0 Subject: Re: [RFC PATCH] Allow optional module parameters 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> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Andy Lutomirski Cc: Jonathan Masters , Rusty Russell , Lucas De Marchi , "linux-kernel@vger.kernel.org" , Ben Hutchings , "linux-kbuild@vger.kernel.org" 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? Thanks, Michal