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+55aFydgX7yejyPq0ckuXabEFhjXO960F=L0-+yYNT=U=Madg@mail.gmail.com>
Date:	Mon, 10 Mar 2014 20:09:40 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	"the arch/x86 maintainers" <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>,
	Dave Jones <davej@...hat.com>
Subject: Re: [PATCH v2] x86: Remove compat vdso support

On Mon, Mar 10, 2014 at 7:37 PM, Andy Lutomirski <luto@...capital.net> wrote:
>
> It does.  My patch breaks OpenSuSE 9 when
> CONFIG_ENABLE_VDSO32_BY_DEFAULT=y unless it's overridden by sysctl or
> boot option.

Oh, I missed that "when =y" part.

But why do we then want to have that "=y" as an option at all?

If the situation is that everybody is fine with that being disabled by
default, let's just make it the default. And I'd even be ok with
removing it as an option *entirely*.

That would seem to be *much* preferable that having an option that
nobody really wants anyway, and where the default value would break
some users. THAT just seems completely insane.

                   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/