From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754287AbbCISQH (ORCPT ); Mon, 9 Mar 2015 14:16:07 -0400 Received: from mail-ie0-f176.google.com ([209.85.223.176]:42692 "EHLO mail-ie0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752449AbbCISQD (ORCPT ); Mon, 9 Mar 2015 14:16:03 -0400 MIME-Version: 1.0 In-Reply-To: References: <1425909943-14687-1-git-send-email-dvlasenk@redhat.com> <54FDDB90.9010706@zytor.com> Date: Mon, 9 Mar 2015 11:16:03 -0700 X-Google-Sender-Auth: GfP2hGo_hL9qfPp0FinXEAd1xx0 Message-ID: Subject: Re: [PATCH] x86: entry_32.S: change ESPFIX test to not touch PT_OLDSS(%esp) From: Linus Torvalds To: Andy Lutomirski Cc: "H. Peter Anvin" , Denys Vlasenko , Steven Rostedt , Ingo Molnar , Borislav Petkov , Oleg Nesterov , Frederic Weisbecker , Alexei Starovoitov , Will Drewry , Kees Cook , "the arch/x86 maintainers" , Linux Kernel Mailing List 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 Mon, Mar 9, 2015 at 11:04 AM, Andy Lutomirski wrote: > > One option would be to change the NMI entry code to move itself down 8 > bytes if this happens (came from kernel mode or sp == sp0 - 12, > perhaps). Hmm. That whole code currently depends on the stack setup being just a single instruction (the move to esp). And that simplifies things, I'd like to keep it that way. I'd *much* rather just keep the 8-byte padding. What was so problematic with that? It worked. It's been around forever. Removing it is the bug. Linus