linux-kernel - NACK! Re: [PATCH 4/4] Add vsyscalls to feature-removal-schedule.txt

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:	Fri, 12 Aug 2011 11:25:15 -0700
From:	Andi Kleen <andi@...stfloor.org>
To:	Andy Lutomirski <luto@....EDU>
Cc:	x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	lueckintel@...oo.com, kimwooyoung@...il.com,
	Ingo Molnar <mingo@...e.hu>, Borislav Petkov <bp@...en8.de>,
	Suresh Siddha <suresh.b.siddha@...el.com>
Subject: NACK! Re: [PATCH 4/4] Add vsyscalls to feature-removal-schedule.txt

Andy Lutomirski <luto@....EDU> writes:

> In a couple years, we'll see how well we've done at eradicating vsyscall-using
> binaries.  Hopefully we can then disable them by default.  We will probably
> have to leave the option to enable them around forever.

NACK NACK NACK!

this would break all old (old = meaning all today's) x86-64 installations. 

Sorry but I don't think feature removal should be ever for anything
commonly used, especially not for anything used by nearly 
EVERY binary on an old installation. We usually use it 
for obscure things used rarely.

Repeat after me: BINARY COMPATIBILITY is important.
It's not a joke. It's not a toy. It's one of the basic values
of Linux.

Sorry to be honest I don't know how you can even suggest
such a thing with a straight face.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only
--
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/