From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751467AbcBLRAP (ORCPT ); Fri, 12 Feb 2016 12:00:15 -0500 Received: from mail.skyhub.de ([78.46.96.112]:46872 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751016AbcBLRAN (ORCPT ); Fri, 12 Feb 2016 12:00:13 -0500 Date: Fri, 12 Feb 2016 18:00:10 +0100 From: Borislav Petkov To: Andy Lutomirski Cc: x86-ml , lkml Subject: Re: WARNING: CPU: 0 PID: 3031 at ./arch/x86/include/asm/fpu/internal.h:530 fpu__restore+0x90/0x130() Message-ID: <20160212170010.GE4099@pd.tnic> References: <20160211192741.GG5565@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 11, 2016 at 05:16:00PM -0800, Andy Lutomirski wrote: > fpu__drop(fpu); > if (__copy_from_user(&fpu->state.xsave, buf_fx, state_size) || > __copy_from_user(&env, buf, sizeof(env))) { > fpstate_init(&fpu->state); > err = -1; > } else { > sanitize_restored_xstate(tsk, &env, xfeatures, fx_only); > } > > fpu->fpstate_active = 1; > > <-- preempted right here >>From IRC: you could try sticking a schedule() right after that fpu->fpstate_active = 1; line > if (use_eager_fpu()) { > preempt_disable(); > fpu__restore(fpu); > preempt_enable(); Something for me to try when I get a chance. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.