linux-kernel - Re: [PATCH 0/2] ftrace: handle NMIs safely

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: <20081030203434.GL27407@elte.hu>
Date:	Thu, 30 Oct 2008 21:34:34 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 0/2] ftrace: handle NMIs safely


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

> The robustness of ftrace has been the focus of the code modification 
> in 2.6.28. There is one remaining issue that needed to be addressed. 
> This was the case of NMIs.

applied to tip/tracing/nmisafe, thanks Steve!

this looks a lot nicer approach than either putting some sort of lock 
into NMI context (yuck) or the disabling of NMIs (not really possible 
in a generic way architecturally).

the impact is quite non-trivial, so i dont think this is v2.6.28 
material.

	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/