linux-kernel - Re: [BUG] gcov causes vread_tsc to increment kernel 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090703071315.GE32687@elte.hu>
Date:	Fri, 3 Jul 2009 09:13:15 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Oberparleiter <oberpar@...ux.vnet.ibm.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [BUG] gcov causes vread_tsc to increment kernel memory


* Peter Oberparleiter <oberpar@...ux.vnet.ibm.com> wrote:

> Also seeing as function tracer and gcov work on a similar basis 
> and require similar files to be excluded from profiling, it would 
> be nice if we wouldn't need to mark those files separately. [...]

One of the general things i pointed out during review is that 
there's a fair amount of overlap between tracing/instrumentation and 
the gcov support patches and now for a change Andrew has merged 
incomplete stuff upstream prematurely ;-) Andrew, could you please 
make sure this all gets fixed and the review suggestions get 
implemented?

	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/