Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751533AbaD3A5N (ORCPT ); Tue, 29 Apr 2014 20:57:13 -0400 Received: from mail-vc0-f181.google.com ([209.85.220.181]:50035 "EHLO mail-vc0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750813AbaD3A5M (ORCPT ); Tue, 29 Apr 2014 20:57:12 -0400 MIME-Version: 1.0 In-Reply-To: <1398816946-3351-1-git-send-email-hpa@linux.intel.com> References: <1398816946-3351-1-git-send-email-hpa@linux.intel.com> Date: Tue, 29 Apr 2014 17:57:11 -0700 X-Google-Sender-Auth: _3SORkMfAO1jAiddHcDMvX7J2_4 Message-ID: Subject: Re: [PATCH] x86-64, espfix: Don't leak bits 31:16 of %esp returning to 16-bit stack From: Linus Torvalds To: "H. Peter Anvin" Cc: Linux Kernel Mailing List , "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , Konrad Rzeszutek Wilk , Borislav Petkov , Andrew Lutomriski , Dirk Hohndel , Arjan van de Ven , comex , Alexander van Heukelum , Boris Ostrovsky 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 Tue, Apr 29, 2014 at 5:15 PM, H. Peter Anvin wrote: > > Linus, this is technically a (functionality) regression fix. Will you > want this for 3.15? Too scary. If people complain, I think we should just replace the if (!ldt_info.seg_32bit) { with something like if (!ldt_info.seg_32bit && !sysctl_allow_16bit_segments) { and handle the regression that way. Then, after way more testing, maybe we can backport the espfix thing. 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/