linux-kernel - Re: [PATCH v2] 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]

Message-ID: <CA+55aFyTCoipjhbAVCuhCgqb8JeSjGcmOU3xE6EFrjNpfspfqg@mail.gmail.com>
Date:	Wed, 12 Mar 2014 07:41:26 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Stefani Seibold <stefani@...bold.net>
Cc:	Andy Lutomirski <luto@...capital.net>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"the arch/x86 maintainers" <x86@...nel.org>,
	Dave Jones <davej@...hat.com>,
	Martin Runge <Martin.Runge@...de-schwarz.com>,
	Andreas Brief <Andreas.Brief@...de-schwarz.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2] x86: Remove compat vdso support

On Wed, Mar 12, 2014 at 1:30 AM, Stefani Seibold <stefani@...bold.net> wrote:
>
> Is it possible to calm down and get a more technical discussion rather
> than blaming and treats not to accepting patches?

I'm just asking for an upside to the changes, and fighting changing
things "just because".

32-bit is not dead in the sense that it doesn't exist any more, but it
*is* dead in the sense that there is absolutely zero point in treating
it as a developing platform. That was very clearly also the context in
which I said "dead, dead, dead", I was objecting to trying to
future-proof things that are not worth future-proofing.

The VDSO code has worked for us for a long time, and I'm upset and
annoyed that people want to do "improvements" to it that are not
improvements at all. They are ugly (just look at that
remap_pfn_range() call in you patch - why?), and they cause problems,
and instead of people saying "ok, fix the source of the problem",
people are running around like headless chicken and saying "ok, let's
work around all these problems".

WHY?

Nobody has even explained why we want this at all, and why we want
this headache. Nobody has explained why the solution is not to "just
don't do that then". Instead, people are piling up *more* complexity
because the patch had a problem.

That's a technical issue, Stefani. And the threat to not apply patches
is a technical solution, and I'm getting more and more convinced is
the *right* technical solution.

And when Fengguang's automatic bug tester found the problem, YOU
STARTED ARGUING WITH HIM.  Christ, well *excuuse* me for being fed up
with this pointless discussion.

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