linux-kernel - Re: lib: turn CONFIG_STACKTRACE into an actual option.

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]

Date:	Wed, 13 Aug 2014 17:57:12 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>, mingo@...e.hu,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: lib: turn CONFIG_STACKTRACE into an actual option.


* Dave Jones <davej@...hat.com> wrote:

> I was puzzled why /proc/$$/stack had disappeared, until I figured out
> I had disabled the last debug option that did a 'select STACKTRACE'.
> This patch makes the option show up at config time, so it can be
> enabled without enabling any of the more heavyweight debug options.
> 
> Signed-off-by: Dave Jones <davej@...hat.com>
> 
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 7a638aa3545b..96c64beac12a 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1008,8 +1008,13 @@ config TRACE_IRQFLAGS
>  	  either tracing or lock debugging.
>  
>  config STACKTRACE
> -	bool
> +	bool "Stack backtrace support"
>  	depends on STACKTRACE_SUPPORT
> +	help
> +	  This option causes the kernel to create a /proc/pid/stack for
> +	  every process, showing its current stack trace.
> +	  It is also used by various kernel debugging features that require
> +	  stack trace generation.
>  
>  config DEBUG_KOBJECT
>  	bool "kobject debugging"

Acked-by: Ingo Molnar <mingo@...nel.org>

Thanks,

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