From: Andi Kleen <andi@firstfloor.org>
To: Andy Lutomirski <luto@MIT.EDU>
Cc: x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
lueckintel@yahoo.com, kimwooyoung@gmail.com,
Ingo Molnar <mingo@elte.hu>, Borislav Petkov <bp@alien8.de>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: NACK! Re: [PATCH 4/4] Add vsyscalls to feature-removal-schedule.txt
Date: Fri, 12 Aug 2011 11:25:15 -0700 [thread overview]
Message-ID: <m24o1mmqr8.fsf_-_@firstfloor.org> (raw)
In-Reply-To: <066852f3f344c1733e0db9a2427981ea1815db7d.1312899174.git.luto@mit.edu> (Andy Lutomirski's message of "Tue, 9 Aug 2011 10:27:50 -0400")
Andy Lutomirski <luto@MIT.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@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2011-08-12 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 14:27 [PATCH 0/4] vsyscall tweaks Andy Lutomirski
2011-08-09 14:27 ` [PATCH 1/4] x86-64: Allow emulated vsyscalls from user addresses Andy Lutomirski
2011-08-09 18:59 ` H. Peter Anvin
2011-08-09 19:16 ` Andrew Lutomirski
2011-08-09 14:27 ` [PATCH 2/4] x86: Remove unnecessary compile flag tweaks for vsyscall code Andy Lutomirski
2011-08-09 14:27 ` [PATCH 3/4] x86-64: Wire up getcpu syscall Andy Lutomirski
2011-08-09 14:27 ` [PATCH 4/4] Add vsyscalls to feature-removal-schedule.txt Andy Lutomirski
2011-08-12 18:25 ` Andi Kleen [this message]
2011-08-12 19:13 ` NACK! " Andrew Lutomirski
2011-08-17 20:35 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m24o1mmqr8.fsf_-_@firstfloor.org \
--to=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kimwooyoung@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lueckintel@yahoo.com \
--cc=luto@MIT.EDU \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox