linux-kernel - Re: [PATCH] ftrace: dump out ftrace buffers to console on panic

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, 30 Jul 2008 21:05:30 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] ftrace: dump out ftrace buffers to console on panic


On Wed, 30 Jul 2008, Andrew Morton wrote:
>>
>> I don't mind making it unconditionally available. I only added the config
>> option because I thought people would like to turn it off.
>>
>> I'll resubmit with the above concerns fixed and without the config option.
>
> Well..  my question about the config option was no more than a question
> - I don't know the answer.
>
> Although thinking about it, I guess that anyone who is really squeezy
> on space just won't be enabling ftrace at all.  Is there any reason
> other than size for disabling this new feature?

Just the output to the console on oops. But then again, it only prints a 
lot if ftrace has stuff in the buffers.

I also lowered the count to keep the pain down when this was configured, 
but since the size of the buffers is both boot time and run time 
configurable, it shouldn't be a problem. If people want more buffer space, 
they simply need to increase it at run time.

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