linux-kernel - Re: [PATCH 4/8] debug printk infrastructure -dynamic printk docs

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] [day] [month] [year] [list]

Message-Id: <20080527144028.83f87adc.akpm@linux-foundation.org>
Date:	Tue, 27 May 2008 14:40:28 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jason Baron <jbaron@...hat.com>
Cc:	joe@...ches.com, greg@...ah.com, nick@...k-andrew.net,
	randy.dunlap@...cle.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/8] debug printk infrastructure -dynamic printk docs

On Thu, 22 May 2008 17:17:23 -0400
Jason Baron <jbaron@...hat.com> wrote:

> 
> Signed-off-by: Jason Baron <jbaron@...hat.com>
> ---
>  Documentation/kernel-parameters.txt |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index bf6303e..d9a1245 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -1580,6 +1580,11 @@ and is between 256 and 4096 characters. It is defined in the file
>  			autoconfiguration.
>  			Ranges are in pairs (memory base and size).
>  
> +	dynamic_printk
> +			Enables pr_debug()/dev_dbg() calls if 
> +			CONFIG_PRINK_DYNAMIC has been enabled. These can also 
> +			be switched on/off via <debugfs>/dynamic_printk/modules
> +

There is no CONFIG_PRINK_DYNAMIC?  I guess you meant
CONFIG_DYNAMIC_PRINTK_DEBUG.

>  	print-fatal-signals=
>  			[KNL] debug: print fatal signals
>  			print-fatal-signals=1: print segfault info to
> -- 
> 1.5.4.5
> 
--
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/