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]

Date:	Mon, 1 Sep 2008 11:47:43 -0400
From:	Jeff Dike <jdike@...toit.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	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 04:22:19PM +0200, Andi Kleen wrote:
> > 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? 

The userspace side of UML can (and, indeed must) use the system
headers.  Here, we can just #include <valgrind.h>.

However, the kernel side of UML, where the allocator annotations are,
can't use system headers.  The kernel side of things has to be
self-contained within the kernel tree.

	       	      	  	 Jeff

-- 
Work email - jdike at linux dot intel dot com
--
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/