[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <536A68B1.6070500@zytor.com>
Date: Wed, 07 May 2014 10:09:05 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Sven Joachim <svenjoac@....de>
CC: Alexandre Julliard <julliard@...ehq.org>,
Brian Gerst <brgerst@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
stable <stable@...r.kernel.org>,
"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit
kernels
On 05/07/2014 09:57 AM, Linus Torvalds wrote:
>
> Afaik, 16-bit programs under wine already need
>
> echo 0 > /proc/sys/vm/mmap_min_addr
>
> because they want to map things at address 0, so this isn't a new concept.
>
I think that applies to DOSEMU, but not to Wine.
Sven: if you have the ability to build your own kernel, could you also
try the "x86/espfix" branch of the git tree:
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/
(clone URLs:)
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
... to make sure the proper solution works for you?
I'm somewhat curious if this program you have is actually a 32-bit
program or if it is really a 16-bit program wrapped in a 32-bit
installer of some kind. Hard to know without seeing the program in
question.
-hpa
--
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