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:	Thu, 9 Jul 2015 12:00:59 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Oleg Nesterov <oleg@...hat.com>,
	Kees Cook <keescook@...omium.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Borislav Petkov <bp@...en8.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Austin S Hemmelgarn <ahferroin7@...il.com>,
	Brian Gerst <brgerst@...il.com>,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: [PATCH] x86/kconfig/32: Make CONFIG_VM86 default to n and remove EXPERT

On Thu, Jul 9, 2015 at 11:51 AM, Arjan van de Ven <arjan@...ux.intel.com> wrote:
> On 7/9/2015 11:40 AM, Andy Lutomirski wrote:
>>
>> VM86 is entirely broken if ptrace, syscall auditing, or NOHZ_FULL is
>> in use.  The code is a big undocumented mess, it's a real PITA to
>> test, and it looks like a big chunk of vm86_32.c is dead code.  It
>> also plays awful games with the entry asm.
>>
>> No one should be using it anyway.  Use DOSBOX or KVM instead.
>>
>> Let's accelerate its slow death.  Remove it from EXPERT and default
>> it to n.  Distros should not enable it.  In the unlikely event that
>> some user needs it, they can easily re-enable it.
>>
>> I've confirmed that 'make oldconfig' will set leave it set to y, so
>> there should be little or no unexpected breakage from this change.
>>
>
> I would rather do BOTH the default n AND the EXPERT
>
> e.g. the existing hurdle of EXPERT combined with the default
> (e.g. off entirely in non-EXPERT, and with EXPERT it is sill defaulting to
> =n)
>
>

I figured we could do this for a release or two, then move it into
EXPERT.  But I'd be fine with your suggestion, too.

Ingo, Linus?

--Andy


-- 
Andy Lutomirski
AMA Capital Management, LLC
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ