Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753166AbaJFQqT (ORCPT ); Mon, 6 Oct 2014 12:46:19 -0400 Received: from mail-lb0-f182.google.com ([209.85.217.182]:61524 "EHLO mail-lb0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752049AbaJFQqS (ORCPT ); Mon, 6 Oct 2014 12:46:18 -0400 MIME-Version: 1.0 In-Reply-To: <5432C62C.704@zytor.com> References: <5432C62C.704@zytor.com> From: Andy Lutomirski Date: Mon, 6 Oct 2014 09:45:56 -0700 Message-ID: Subject: Re: [PATCH v4 0/2] x86_64,entry: Clear NT on entry and speed up switch_to To: "H. Peter Anvin" Cc: Thomas Gleixner , X86 ML , Ingo Molnar , Sebastian Lackner , Anish Bhatt , "linux-kernel@vger.kernel.org" , Chuck Ebbert 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, Oct 6, 2014 at 9:41 AM, H. Peter Anvin wrote: > On 10/06/2014 09:39 AM, Andy Lutomirski wrote: >> On Wed, Oct 1, 2014 at 11:49 AM, Andy Lutomirski wrote: >>> Anish Bhatt noticed that user programs can set RFLAGS.NT before >>> syscall or sysenter, and the kernel entry code doesn't filter out >>> NT. This causes kernel C code and, depending on thread flags, the >>> exit slow path to run with NT set. >>> >> >> Quick ping: now that the merge window is (sort of) open, what's >> happening with these patches? >> >> Thanks, >> Andy >> > > My preference would be to queue them up for 3.19 since they arrived late > in the 3.18 cycle. I see nothing wrong with deferring patch 2 for 3.19, but deferring patch 1, which is tagged for stable, for an entire release seems a bit silly to me. --Andy -- 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/