linux-kernel - Re: disable "Call Trace:"

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: <53E5A27A.90409@infradead.org>
Date:	Fri, 08 Aug 2014 21:24:26 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	積丹尼 Dan Jacobson <jidanni@...anni.org>,
	linux-kernel@...r.kernel.org
Subject: Re: disable "Call Trace:"

On 08/07/14 20:05, 積丹尼 Dan Jacobson wrote:
> Idea: if the user could disable
> the "Call Trace:"
> seen upon "Kernel panic - not syncing: attempted to kill init!"
> he would then be able to see more lines above without having it shoved
> off the screen with the useless (to him) call trace.

When would you want to disable it?  at kernel boot time (as a boot option)
or sometime later?

> e.g., using panic=222 call_trace=disabled would give him enough time and room
> to read more of what happened from the screen.
> --

Makes some sense to me and it's not difficult to implement.

But would you only want to disable Call Trace: on panics or any time that a
call trace might be printed?  and would disabling call trace also disable
the raw stack dump and Code: output, or literally just the call trace?


-- 
~Randy
--
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/