linux-kernel - Re: [PATCH] tracing/function-return-tracer: Add a barrier to ensure return stack index is incremented in memory

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: <20081116064304.GC32215@elte.hu>
Date:	Sun, 16 Nov 2008 07:43:04 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH] tracing/function-return-tracer: Add a barrier to
	ensure return stack index is incremented in memory


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> Impact: Fix possible race condition in ftrace function return tracer
> 
> This fixes a possible race condition if index incrementation
> is not immediately flushed in memory.
> 
> Thanks for Andi Kleen and Steven Rostedt for pointing out this issue
> and give me this solution.
> 
> Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
> Cc: Steven Rostedt <rostedt@...dmis.org>

applied, thanks Frederic!

	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/