linux-kernel - [PATCH 0/3] ftrace: code consolidation

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-next>] [day] [month] [year] [list]

Date:	Mon, 03 Nov 2008 23:15:54 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH 0/3] ftrace: code consolidation

[ For 2.6.29 ]

The first two patches makes ftrace function calling and other
sensitive tracing use a macro to handle preemption disabling.
This removes a lot of duplicate code that works on preventing
the scheduler from infinite recursion.

The last patch sets an easy way for the user to either use
irq disabling or preemption disabing for the function tracer.

Peter Zijlstra noticed a bit of a trace that was not showing
up due to lost traces caused by interrupts when the function
tracer was running.

Due to the sensitive nature of the function tracer, it can
not allow for recursive tracing, so it needs to disable
recursion while it records the trace. But this also means
that without disabling interrupts, any interrupt that happens
while the trace is happening will be lost from the trace
itself.

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