linux-kernel - Re: [PATCH] ftrace: only trace preempt off with preempt tracer

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]

Message-ID: <20080718165755.GG6875@elte.hu>
Date:	Fri, 18 Jul 2008 18:57:55 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] ftrace: only trace preempt off with preempt tracer


* Steven Rostedt <rostedt@...dmis.org> wrote:

> When PREEMPT_TRACER and IRQSOFF_TRACER are both configured and irqsoff 
> tracer is running, the preempt_off sections might also be traced.
> 
> Thanks to Andrew Morton for pointing out my mistake of spin_lock 
> disabling interrupts while he was reviewing ftrace.txt. Seems that my 
> example I used actually hit this bug.

applied to tip/tracing/urgent - thanks Steve.

	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/