From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Alexandre Julliard To: "H. Peter Anvin" Cc: Linus Torvalds , Sven Joachim , Brian Gerst , Ingo Molnar , Linux Kernel Mailing List , Thomas Gleixner , stable , "H. Peter Anvin" Subject: Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels References: <87k3aspd1h.fsf@wine.dyndns.org> <87zjiuymiu.fsf@turtle.gmx.de> <536A68B1.6070500@zytor.com> Date: Wed, 07 May 2014 19:50:18 +0200 In-Reply-To: <536A68B1.6070500@zytor.com> (H. Peter Anvin's message of "Wed, 07 May 2014 10:09:05 -0700") Message-ID: <87eh05fpgl.fsf@wine.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: "H. Peter Anvin" writes: > 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. Yes, there are a few exceptions, but most Win16 apps run fine without mapping address 0. > 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. It could be a mix of both, there are various thunking mechanisms that allow 32-bit binaries to use 16-bit components. This was pretty common in the Win95 days. -- Alexandre Julliard julliard@winehq.org