linux-kernel - Re: [PATCH] x86/asm/msr: Retract msr-index.h

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: <556F4DE1.8070706@zytor.com>
Date:	Wed, 03 Jun 2015 11:56:33 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...en8.de>, LKML <linux-kernel@...r.kernel.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Andy Lutomirski <luto@...nel.org>,
	Ingo Molnar <mingo@...nel.org>,
	"Peter Zijlstra (Intel)" <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
	David Howells <dhowells@...hat.com>,
	Len Brown <lenb@...nel.org>
Subject: Re: [PATCH] x86/asm/msr: Retract msr-index.h

On 06/03/2015 11:21 AM, Borislav Petkov wrote:
> On Wed, Jun 03, 2015 at 02:41:48PM +0200, Borislav Petkov wrote:
>> This header containing all MSRs and respective bit definitions got
>> exported to userspace in conjunction with the big uapi shuffle.
>>
>> But, it doesn't have anything to do in the uapi headers because
>> userspace can do its own MSR defines and exporting them from the
>> kernel blocks us from doing cleanups/renames in that header. Which is
>> ridiculous - it is not kernel's job to export such a header and keep
>> MSRs list and their names stable.
> 
> Here's v2. Needed to *not* include it into uapi/asm/msr.h either.

I really like the patch, but the description is awful.

How about: "x86/uapi: <asm/msr.h> is not a UAPI"

	-hpa


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