linux-kernel - Re: [PATCH 1/6] base: Valgrind headers and Kconfig

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: <20080901142219.GH18288@one.firstfloor.org>
Date:	Mon, 1 Sep 2008 16:22:19 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Jeff Dike <jdike@...toit.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Steve VanDeBogart <vandebo-lkml@...dBox.Net>,
	linux-kernel@...r.kernel.org,
	user-mode-linux-devel@...ts.sourceforge.net, jiayingz@...gle.com,
	dkegel@...gle.com
Subject: Re: [PATCH 1/6] base: Valgrind headers and Kconfig

On Mon, Sep 01, 2008 at 10:06:18AM -0400, Jeff Dike wrote:
> On Mon, Sep 01, 2008 at 11:32:00AM +0200, Andi Kleen wrote:
> > Steve VanDeBogart <vandebo-lkml@...dBox.Net> writes:
> > > Kconfig option for Valgrind.  Suppression file, for known non-issues.
> > > Valgrind header files (svn 8534) that define the client request
> > > mechanism used to annotate programs plus a couple lines to integrate
> > > with Kconfig.
> > 
> > Couldn't you just get the valgrind.h header from the currently
> > installed valgrind? UML relies on host includes anyways, so
> > I don't see a reason to not do that for valgrind too.
> 
> Kernel code can't get headers from the system, unless you're thinking
>        #include "/usr/include/valgrind.h"
> or something similar.

Some um files at least least include sys/* files which are surely
user space?  If they can include that why not valgrind.h? 


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