linux-kernel - Re: [PATCH 4/9] ftrace: Add enable/disable ftrace

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: <1322510741.2921.169.camel@twins>
Date:	Mon, 28 Nov 2011 21:05:41 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Jiri Olsa <jolsa@...hat.com>, fweisbec@...il.com, mingo@...hat.com,
	paulus@...ba.org, acme@...stprotocols.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/9] ftrace: Add enable/disable ftrace_ops control
 interface

On Mon, 2011-11-28 at 21:02 +0100, Peter Zijlstra wrote:
> On Mon, 2011-11-28 at 14:26 -0500, Steven Rostedt wrote:
> > 
> > Are jump labels safe in NMI context yet? If not, this will need to wait
> > till we make it so. 
> 
> I don't think they are, we currently very much rely on that
> stop_machine() crap. NMIs can go straight through that.
> 
> I think you can make it work with the stop_machine()-less approach,
> because then the NMI will trap on the INT3 which will wait for
> completion, sync and resume the NMI.

Note that this of course precludes ever using jump_labels from do_int3
handlers ;-)
--
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/