linux-kernel - Re: [00/11] pr_debug during module initialization

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]

Date:	Fri, 23 Mar 2012 16:27:13 -0400
From:	Jason Baron <jbaron@...hat.com>
To:	jim.cromie@...il.com
Cc:	rusty@...tcorp.com.au, linux-kernel@...r.kernel.org
Subject: Re: [00/11] pr_debug during module initialization

On Wed, Mar 14, 2012 at 05:01:55PM -0600, jim.cromie@...il.com wrote:
> This is 3rd revision of the dyndbg modinit patches, previously sent
> Dec 11.  Patches 1-17/25 sent then were added to driver-core-next,
> this set reworks the remainder.
> 
> It implements the "fake" module param approach proposed by
> Thomas Renninger, back in https://lkml.org/lkml/2010/9/15/397
> 

Hi,

I'm wondering, if we leave the cmdline parameter: 'ddebug_query=' around
for a bit before removing it, so it doesn't get dropped too suddenly.
Perhaps, we add a warning msg, for people that are still using it
for a few releases warning that it is deprecated, before dropping it.

Also, let's add the 'dyndbg=' syntax to Documentation/kernel-parameters.txt.

A previous version had a build-time error if a module used 'dyndbg' as a
module param - why did that get dropped?

Thanks!

-Jason
--
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/