From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932352AbbEHRmT (ORCPT ); Fri, 8 May 2015 13:42:19 -0400 Received: from www.sr71.net ([198.145.64.142]:47624 "EHLO blackbird.sr71.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932237AbbEHRmP (ORCPT ); Fri, 8 May 2015 13:42:15 -0400 Message-ID: <554CF574.8090409@sr71.net> Date: Fri, 08 May 2015 10:42:12 -0700 From: Dave Hansen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Borislav Petkov CC: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de, dave.hansen@linux.intel.com, oleg@redhat.com, riel@redhat.com, sbsiddha@gmail.com, luto@amacapital.net, mingo@redhat.com, hpa@zytor.com, fenghua.yu@intel.com Subject: Re: [PATCH 01/17] x86, fpu: wrap get_xsave_addr() to make it safer References: <20150422182729.0512E57D@viggo.jf.intel.com> <20150422182731.4E4F8448@viggo.jf.intel.com> <20150425093119.GD32099@pd.tnic> <20150505172753.GN3910@pd.tnic> In-Reply-To: <20150505172753.GN3910@pd.tnic> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.