From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753986AbcEIXsr (ORCPT ); Mon, 9 May 2016 19:48:47 -0400 Received: from mga09.intel.com ([134.134.136.24]:62963 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751147AbcEIXsp (ORCPT ); Mon, 9 May 2016 19:48:45 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,602,1455004800"; d="scan'208";a="949595357" Date: Mon, 9 May 2016 16:44:17 -0700 From: Yu-cheng Yu To: Dave Hansen Cc: linux-kernel@vger.kernel.org, x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , Andy Lutomirski , Borislav Petkov , Sai Praneeth Prakhya , "Ravi V. Shankar" , Fenghua Yu Subject: Re: [PATCH v5 11/13] x86/xsaves: Add WARN_ON_FPU() when a disabled xstate component offset is requested for a compacted format Message-ID: <20160509234416.GA28442@test-lenovo> References: <57311DC6.5000503@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57311DC6.5000503@linux.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 09, 2016 at 04:31:18PM -0700, Dave Hansen wrote: > On 05/09/2016 01:46 PM, Yu-cheng Yu wrote: > > Add a warning in case a disabled (not existing) xstate component offset > > is requested. > ... > > diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c > > index 350814c..2e6dbfe 100644 > > --- a/arch/x86/kernel/fpu/xstate.c > > +++ b/arch/x86/kernel/fpu/xstate.c > > @@ -756,6 +756,7 @@ void *__raw_xsave_addr(struct xregs_state *xsave, int xstate_feature_mask) > > { > > int feature_nr = fls64(xstate_feature_mask) - 1; > > > > + WARN_ON_FPU(using_compacted_format() && !xfeature_enabled(feature_nr)); > > return (void *)xsave + xstate_comp_offsets[feature_nr]; > > } > > Why the using_compacted_format()? Shouldn't this be an error, regardless. If the kernel is not using compacted format, I can get a component offset, no? > > Also, what is xstate_comp_offsets[feature_nr] in this case? Isn't it > -1? Should we be returning NULL along with WARN()ing? NULL makes sense. I will change it.