linux-kernel - Re: [PATCH] x86: Remove compat vdso support

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, 10 Mar 2014 17:19:27 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	"H. Peter Anvin" <hpa@...ux.intel.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	X86 ML <x86@...nel.org>, Stefani Seibold <stefani@...bold.net>,
	Andreas Brief <Andreas.Brief@...de-schwarz.com>,
	Martin Runge <Martin.Runge@...de-schwarz.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Remove compat vdso support

On Mon, Mar 10, 2014 at 5:13 PM, H. Peter Anvin <hpa@...ux.intel.com> wrote:
> On 03/10/2014 05:12 PM, Andy Lutomirski wrote:
>> The compat vDSO is a complicated hack that's needed to maintain
>> compatibility with a small range of never-released glibc versions.
>>
>> This removes it and replaces it with a much simpler hack: a config
>> option to disable the 32-bit vDSO by default.
>>
>> Signed-off-by: Andy Lutomirski <luto@...capital.net>
>
> Can we verify this works correctly on the affected distributions?

It works correctly on Fedora 20 32-bit and 64-bit.

I don't actually know what the affected distribution is, which makes
it hard.  But it would be rather surprising if it didn't, since I
suspect people would have noticed and complained very quickly and
loudly if there was ever a glibc version that didn't work without a
vDSO.

TBH, I'd be more surprised if this breaks anything than I'd be if
current kernels are already broken.

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