From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751359AbaDLEo0 (ORCPT ); Sat, 12 Apr 2014 00:44:26 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:55263 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750930AbaDLEoX (ORCPT ); Sat, 12 Apr 2014 00:44:23 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 12 Apr 2014 00:44:22 -0400 Message-ID: Subject: Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels From: Brian Gerst To: Linus Torvalds Cc: Ingo Molnar , "H. Peter Anvin" , Linux Kernel Mailing List , Thomas Gleixner , stable , "H. Peter Anvin" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 11, 2014 at 2:50 PM, Linus Torvalds wrote: > On Fri, Apr 11, 2014 at 11:45 AM, Brian Gerst wrote: >> >> I haven't tested it recently but I do know it has worked on 64-bit >> kernels. There is no reason for it not to, the only thing not >> supported in long mode is vm86. 16-bit protected mode is unchanged. > > Afaik 64-bit windows doesn't support 16-bit binaries, so I just > assumed Wine wouldn't do it either on x86-64. Not for any real > technical reasons, though. > > HOWEVER. I'd like to hear something more definitive than "I haven't > tested recently". The "we don't break user space" is about having > actual real *users*, not about test programs. > > Are there people actually using 16-bit old windows programs under > wine? That's what matters. > > Linus I just verified that the game does still run on a 64-bit kernel (3.13.8-200.fc20.x86_64). It needed an older version of Wine, but that's a Wine regression and not kernel related.