linux-kernel - Re: [PATCH 8/8] driver-core: allow enabling async probing for all modules and builtins

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150520072734.GA13083@kroah.com>
Date:	Wed, 20 May 2015 00:27:34 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	"Luis R . Rodriguez" <mcgrof@...e.com>, Tejun Heo <tj@...nel.org>,
	linux-kernel@...r.kernel.org,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Olof Johansson <olof@...om.net>,
	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Subject: Re: [PATCH 8/8] driver-core: allow enabling async probing for all
 modules and builtins

On Mon, Mar 30, 2015 at 04:20:10PM -0700, Dmitry Torokhov wrote:
> From: "Luis R. Rodriguez" <mcgrof@...e.com>
> 
> Folks wishing to test enabling async probe for all built-in drivers
> and/or for all modules can use
> __DEBUG__kernel_force_builtin_async_probe or
> __DEBUG__kernel_force_modules_async_probe kernel parameters.
> 
> Activating either one will taint your kernel.
> 
> Signed-off-by: Luis R. Rodriguez <mcgrof@...e.com>
> [Dmitry: split off from another patch, split into 2 parameters, moved
> over to core_param_unsafe()]
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@...il.com>

I've dropped this from my tree as I don't want to add these options,
only to have to remove them later on when it's found out that these were
a bad idea.

I don't want to create a user api that we have to keep around for
forever, and this would be such a thing (specifying how the kernel
probing works.)  For debugging, can't you just patch up your kernel and
test this out?  What's the real use of this?  Who do you want to enable
these?  And why?  What will you do with the information?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/