From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755220AbbHDDzP (ORCPT ); Mon, 3 Aug 2015 23:55:15 -0400 Received: from mail.skyhub.de ([78.46.96.112]:41989 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754745AbbHDDzN (ORCPT ); Mon, 3 Aug 2015 23:55:13 -0400 Date: Tue, 4 Aug 2015 05:54:51 +0200 From: Borislav Petkov To: Andy Lutomirski Cc: Willy Tarreau , Andy Lutomirski , Kees Cook , Steven Rostedt , "security@kernel.org" , X86 ML , Sasha Levin , LKML , Konrad Rzeszutek Wilk , Boris Ostrovsky , Andrew Cooper , Jan Beulich , xen-devel Subject: Re: [PATCH 2/2] x86/ldt: allow to disable modify_ldt at runtime Message-ID: <20150804035451.GC31787@nazgul.tnic> References: <1438626217-23970-1-git-send-email-w@1wt.eu> <1438626217-23970-3-git-send-email-w@1wt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 03, 2015 at 11:45:24AM -0700, Andy Lutomirski wrote: > P.P.P.S. Who thought that IRET faults unmasking NMIs made any sense > whatsoever when NMIs run on an IST stack? Seriously, people? What happened with asking Intel for a sane IRET-NG? Should be relatively easy - take the current IRET microcode, get rid of the nasty crap, allocate a new opcode and done. Validation should actually have *less* to do and can reuse all current test cases. :-) -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --