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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 09 Aug 2014 12:36:52 +0800
From:	積丹尼 Dan Jacobson <jidanni@...anni.org>
To:	Randy Dunlap <rdunlap@...radead.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: disable "Call Trace:"

>>>>> "RD" == Randy Dunlap <rdunlap@...radead.org> writes:

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

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

All I know is e.g., somehow something went wrong and the user finds
himself unable to boot and unable to read the reason, as Linux is famous
for not having a way to scroll messages that have flown off the screen
and boot_delay= doesn't work good and he doesn't own another terminal he
can plug into a port or even have a port etc. etc. etc.

And he is sitting there and there is the reason, the main body of which
has just flown off the screen.

All pushed off due to this (useless to him) "Call Trace:" and some other
hex stuff lying above "Call Trace".

So if only he could please be able to, there hitting "e" in Grub,
be able to add so "call_trace=no_thanks" "other_hex_stuff=no_thanks"
to that linux command line, so then on the next run there will be
something more left upon the screen! Thank you!
--
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/