public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Crawford <psc@sat.dundee.ac.uk>
To: Stas Sergeev <stsp@list.ru>,
	Andrew Bird <ajb@spheresystems.co.uk>,
	linux-msdos@vger.kernel.org
Subject: Re: Ubuntu 16.04 on i386 has VM86 disabled again
Date: Tue, 26 Apr 2016 10:17:43 +0100	[thread overview]
Message-ID: <571F3237.2080201@sat.dundee.ac.uk> (raw)
In-Reply-To: <571E12FD.8070607@list.ru>

On 25/04/16 13:52, Stas Sergeev wrote:
> That was the "right" thing to do. Or at least justified and discussed.
> If we want vm86(), we need to re-implement it properly.
> I have a word from top linux devs (including Linus himself)
> that properly implemented vm86() will stay enabled.

This may seem like a strange question, but what is actually wrong with 
the current/past vm86() support?

I was under the impression that for 32-bit CPU operation it was simply a 
call to the corresponding x86 instructions, so don't see what would be 
"wrong" with that beyond the obvious aspect that it can be abused by 
malware (much like anything else really) hence the idea of having it 
configurable at run-time so it defaults to being off but is only a 
(root) text edit away from being enabled for us who want it for odd 
cases like dosemu.

Of course 64-bit is more of a problem...

Regards,
Paul

  reply	other threads:[~2016-04-26  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 12:16 Ubuntu 16.04 on i386 has VM86 disabled again Andrew Bird
2016-04-25 12:52 ` Stas Sergeev
2016-04-26  9:17   ` Paul Crawford [this message]
2016-04-26 10:09     ` Andrew Bird
2016-04-26 10:59       ` Stas Sergeev
2016-06-11  8:40         ` Andrew Bird
2016-04-26 10:43     ` Stas Sergeev

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=571F3237.2080201@sat.dundee.ac.uk \
    --to=psc@sat.dundee.ac.uk \
    --cc=ajb@spheresystems.co.uk \
    --cc=linux-msdos@vger.kernel.org \
    --cc=stsp@list.ru \
    /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