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: <50AAB6AF.60806@zytor.com>
Date:	Mon, 19 Nov 2012 14:46:07 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Andy Lutomirski <luto@...capital.net>
CC:	Josh Triplett <josh@...htriplett.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	John Stultz <john.stultz@...aro.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 52/58] x86: vdso: Add prototypes for __vdso_* functions

On 11/19/2012 02:44 PM, Andy Lutomirski wrote:
>>>
>>> Acked-by: Andy Lutomirski <luto@...capital.net>
>>>
>>> In theory, this could go in arch/x86/include/uapi/asm/vdso.h.  No one
>>> cares, I suspect, since there exactly two non-test-case users that I
>>> know of.
>>
>> If you think it makes sense to put the VDSO prototypes in that UAPI
>> header, I could prepare an alternate patch that does so.
> 
> That header doesn't actually exist.  Feel free to create it if you're
> feeling ambitious :)
> 

It would indeed be good to separate out the UAPI for the vdso.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ