linux-kernel - Re: [PATCHv2] x86 trace: Fix page fault tracing bug

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]

Date:	Fri, 28 Feb 2014 11:23:17 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Jiri Olsa <jolsa@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Seiji Aguchi <seiji.aguchi@....com>,
	Vince Weaver <vincent.weaver@...ne.edu>
Subject: Re: [PATCHv2] x86 trace: Fix page fault tracing bug

On Fri, 28 Feb 2014 08:11:59 -0800
"H. Peter Anvin" <hpa@...or.com> wrote:

> If so, do we need to hoist the reading of %cr2 all the way into assembly
> or something else?

Function tracing code should not fault. Peter and Jiri were discussing
on IRC to make sure that perf could not enable userspace stack tracing
for function tracing.

At this point, I would say, lets get rid of any users of function
tracing callbacks that can fault. There callbacks are limited in
context even more so than any other context (faults, interrupts, and
NMIs).

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