linux-kernel - Re: [RFC] [PATCH] Kconfig: enlarge printk buffer size limit

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: <20070302091113.1920ca0f.randy.dunlap@oracle.com>
Date:	Fri, 2 Mar 2007 09:11:13 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	dedekind@...radead.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] [PATCH] Kconfig: enlarge printk buffer size limit

On Fri, 02 Mar 2007 15:27:48 +0200 Artem Bityutskiy wrote:

> From: Artem Bityutskiy <artem.bityutskiy@...ia.com>
> Subject: [RFC] [PATCH] Kconfig: enlarge printk buffer size limit
> 
> This patch makes the upper kernel ring buffer size limit larger. It
> is often very handy to have huge ring-buffer for debugging purposes,
> when the subsystem which is being debugged produces large amount of
> useful output.
> 
> Index: ubi-2.6.git/lib/Kconfig.debug
> ===================================================================
> --- ubi-2.6.git.orig/lib/Kconfig.debug
> +++ ubi-2.6.git/lib/Kconfig.debug
> @@ -79,7 +79,7 @@ config DEBUG_KERNEL
>  
>  config LOG_BUF_SHIFT
>  	int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
> -	range 12 21
> +	range 12 26
>  	default 17 if S390 || LOCKDEP
>  	default 16 if X86_NUMAQ || IA64
>  	default 15 if SMP

That's simple enough, but you could also just add
	log_buf_len=huge_number
or
	log_buf_len=500M
or
	log_buf_len=1G
(for megabytes or gigabytes) to the kernel boot command line.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/