linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Andy Lutomirski <luto@kernel.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Oleg Nesterov <oleg@redhat.com>,
	Kees Cook <keescook@chromium.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Borislav Petkov <bp@alien8.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] x86/kconfig/32: Mark CONFIG_VM86 as BROKEN
Date: Tue, 07 Jul 2015 19:33:34 -0700	[thread overview]
Message-ID: <559C8BFE.6050604@linux.intel.com> (raw)
In-Reply-To: <23d4709cee2fe92c32d41b99c7a3c1823725925a.1436312944.git.luto@kernel.org>

On 7/7/2015 6:25 PM, 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.
>
> Mark it BROKEN.  I want to remove some (obviously incorrect) exit
> asm that it depends on, and I don't want to figure out how to run
> severely obsolete programs just to test something that no one uses
> for anything other than exploits anyway.
>

while it is never great to deprecate features, in this case I am not sure
there is another choice unless someone steps up to seriously revamp this code.
(and look at it from a PREEMPT, NO_HZ etc etc angle)

if this patch would not be acceptable, at minimum we need some sort of "off by default
unless the sysadmin flips a sysfs thing", which is really just a huge hack.


so for me this is

Acked-by: Arjan van de Ven <arjan@linux.intel.com>



  reply	other threads:[~2015-07-08  2:33 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08  1:25 [PATCH] x86/kconfig/32: Mark CONFIG_VM86 as BROKEN Andy Lutomirski
2015-07-08  2:33 ` Arjan van de Ven [this message]
2015-07-08 14:00   ` Thomas Gleixner
2015-07-08 14:04     ` Ingo Molnar
2015-07-09  9:03     ` Pavel Machek
2015-07-09 17:57       ` Andy Lutomirski
2015-07-09 18:03         ` Kees Cook
2015-07-09 18:30         ` Linus Torvalds
2015-07-08 16:59   ` Linus Torvalds
2015-07-08 17:30     ` Andy Lutomirski
2015-07-08 17:49       ` Andy Lutomirski
2015-07-08 17:55         ` Linus Torvalds
2015-07-08 18:47           ` Andy Lutomirski
2015-07-08 18:53             ` Kees Cook
2015-07-08 18:48           ` Kees Cook
2015-07-08 19:04             ` Andy Lutomirski
2015-07-08 18:54           ` Austin S Hemmelgarn
2015-07-08 19:05       ` Brian Gerst
2015-07-08 19:14         ` Andy Lutomirski
2015-07-08 19:39           ` Brian Gerst
2015-07-08 19:59             ` Andy Lutomirski
2015-07-09  5:52               ` Ingo Molnar
2015-07-09  5:59                 ` Ingo Molnar
2015-07-09 18:33                   ` Andy Lutomirski
2015-07-10 11:16                     ` Paolo Bonzini
2015-07-10 14:13                       ` Ingo Molnar
2015-07-10 14:24                         ` Paolo Bonzini
2015-07-10 14:39                       ` Andy Lutomirski
2015-07-10 14:12       ` Eric W. Biederman
2015-07-10 14:37         ` Andy Lutomirski
2015-07-10 16:35           ` Linus Torvalds
2015-07-10 16:44             ` Andy Lutomirski
2015-07-10 17:04               ` Linus Torvalds
2015-07-10 17:13                 ` Andy Lutomirski
2015-07-10 17:39                   ` Linus Torvalds
2015-07-10 17:58                     ` Andy Lutomirski
2015-07-10 18:00                     ` Al Viro
2015-07-11  9:18                     ` Ingo Molnar
2015-07-08 19:13     ` Ingo Molnar
2015-07-08  9:45 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2015-07-08 15:32 ` [PATCH] " Brian Gerst

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=559C8BFE.6050604@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).