Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756526AbaDLVyA (ORCPT ); Sat, 12 Apr 2014 17:54:00 -0400 Received: from mail-ve0-f180.google.com ([209.85.128.180]:64420 "EHLO mail-ve0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755933AbaDLVx5 (ORCPT ); Sat, 12 Apr 2014 17:53:57 -0400 MIME-Version: 1.0 In-Reply-To: <21a22ace-fbc3-4f97-a277-9cdf4f2253eb@email.android.com> References: <6f5f98f2-aa96-433f-9ee8-5ba216624957@email.android.com> <20140412193541.GA30697@pd.tnic> <21a22ace-fbc3-4f97-a277-9cdf4f2253eb@email.android.com> Date: Sat, 12 Apr 2014 14:53:56 -0700 X-Google-Sender-Auth: 8BgOajMAzyAz9OJVjcmXbwidLfE Message-ID: Subject: Re: [tip:x86/urgent] x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels From: Linus Torvalds To: "H. Peter Anvin" Cc: Borislav Petkov , Brian Gerst , Ingo Molnar , 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 Sat, Apr 12, 2014 at 12:44 PM, H. Peter Anvin wrote: > Run a 32-bit VM. The 32-bit kernel does this right. I really don't think that's the answer. If people really run these 16-bit programs, we need to allow it. Clearly it used to work. Just make the unconditional "don't allow 16-bit segments" be a sysconf entry. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/