linux-kernel - Re: [PATCH 1/2] x86: Provide a comment in uapi/asm/hw

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: <20121024103559.GB10691@gmail.com>
Date:	Wed, 24 Oct 2012 12:35:59 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	David Howells <dhowells@...hat.com>
Cc:	tglx@...utronix.de, x86@...nel.org, linux-kernel@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 1/2] x86: Provide a comment in uapi/asm/hw_breakpoint.h


* David Howells <dhowells@...hat.com> wrote:

> Provide a comment in the empty uapi/asm/hw_breakpoint.h to make sure that the
> patch program doesn't delete it.
> 
> However, should some part of asm/hw_breakpoint.h actually be exported here,
> or, possibly, should the entire uapi file be removed?  In v3.6, though the
> file was marked for export to userspace, it had nothing outside of __KERNEL__.
> 
> This needs to be applied on top of the x86 UAPI disintegration patch.

Just wondering, have the tools/perf/ issues been solved in your 
tree, are the x86 UAPI disintegration changes pullable?

Thanks,

	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/