linux-kernel - Re: [PATCH 01/17] x86, fpu: wrap get_xsave

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <554CF574.8090409@sr71.net>
Date:	Fri, 08 May 2015 10:42:12 -0700
From:	Dave Hansen <dave@...1.net>
To:	Borislav Petkov <bp@...en8.de>
CC:	linux-kernel@...r.kernel.org, x86@...nel.org, tglx@...utronix.de,
	dave.hansen@...ux.intel.com, oleg@...hat.com, riel@...hat.com,
	sbsiddha@...il.com, luto@...capital.net, mingo@...hat.com,
	hpa@...or.com, fenghua.yu@...el.com
Subject: Re: [PATCH 01/17] x86, fpu: wrap get_xsave_addr() to make it safer

On 05/05/2015 10:27 AM, Borislav Petkov wrote:
> Yeah, I said "Applied" but didn't know at the time Ingo was doing the
> big FPU cleanup:
> 
> https://lkml.kernel.org/r/1430843228-13749-1-git-send-email-mingo@kernel.org
> 
> So let's wait until the dust settles, I think rediffing this patch
> should be easy and simply made to call fpu__save() which is the new name
> but we'll have to doublecheck.

Hi Borislav,

This fixes a bug present in kernels today.  Until we have an ETA for
Ingo's stuff to get merged, I'd really hope you can consider taking
bugfixes like these.

BTW, I didn't really expect you to pull this in directly.  I think it's
easier if the entire MPX set is pulled in at once.  Otherwise, the x86
maintainers will have to drop this from the set before merging, and it
might not be 100% obvious how this patch got merged via another route.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/