linux-kernel - Re: [PATCH][GIT PULL] x86/function-graph: fix constraint for recording old return value

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]

Date:	Fri, 15 May 2009 16:42:26 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>, stable@...nel.org
Subject: Re: [PATCH][GIT PULL] x86/function-graph: fix constraint for
	recording old return value


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

> Ingo,
> 
> After upgrading my distcc boxes from gcc 4.2.2 to 4.4.0, function 
> graph tracer broke. Seems that the variable "old" needs to be 
> denoted as an "early clobber". I've put this against the urgent 
> tree and I'm Cc'ing stable because by the time 30 (and other) 
> kernels get to users, they may be using gcc 4.4.0. I would expect 
> that we will get more complaints about this as more people start 
> using the newer gcc.
> 
> -- Steve
> 
> 
> Please pull the latest tip/tracing/urgent tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/urgent
> 
> 
> Steven Rostedt (1):
>       x86/function-graph: fix constraint for recording old return value
> 
> ----
>  arch/x86/kernel/ftrace.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

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