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, 15 Oct 2012 09:56:22 +0100
From:	David Howells <dhowells@...hat.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	dhowells@...hat.com,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	paulus@...ba.org, davem@...emloft.net, jaxboe@...ionio.com,
	tj@...nel.org, viro@...iv.linux.org.uk,
	linux-kernel@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] perf: Fix UAPI fallout

Ingo Molnar <mingo@...nel.org> wrote:

> Arnaldo: the way we include some of the include files directly 
> into tools/perf/ .c files [such as hw_breakpoint.h] and 
> represent others transparently via utils/include/ [such as 
> rbtree.h] is a bit messy and ought to be cleaned up I suspect.

I tried to make the USERINCLUDE macro in the bottom-level Makefile that, but I
didn't realise I had to export it:-(.

That, however, also brings in linux/kconfig.h but I don't know whether you
want/need that.

> I think the best model would be to cleanly separate from any 
> /usr/include/linux/ muck, which might be out of sync, and which 
> might stand in the way of changes. Is it possible to exclude all 
> of /usr/include/ and try to build purely from 
> include/uapi/linux/

You would also need arch/foo/include/uapi/.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ