lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 06 Oct 2014 09:57:22 -0700
From:	"H. Peter Anvin" <>
To:	Andy Lutomirski <>
CC:	Thomas Gleixner <>, X86 ML <>,
	Ingo Molnar <>,
	Sebastian Lackner <>,
	Anish Bhatt <>,
	"" <>,
	Chuck Ebbert <>
Subject: Re: [PATCH v4 0/2] x86_64,entry: Clear NT on entry and speed up switch_to

On 10/06/2014 09:45 AM, Andy Lutomirski wrote:
> 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.

Yes, that is probably going to get pushed later in this merge window;
that is usually how we deal with that sort of thing.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists