From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758780AbdCVGRD (ORCPT ); Wed, 22 Mar 2017 02:17:03 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:52776 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757351AbdCVGQ7 (ORCPT ); Wed, 22 Mar 2017 02:16:59 -0400 Date: Wed, 22 Mar 2017 07:10:21 +0100 From: Greg KH To: "Cai, Jason" Cc: "stable@vger.kernel.org" , "kernelnewbies@nl.linux.org" , "linux-kernel@vger.kernel.org" Subject: Re: Linux 3.2: FPU Issue in execve with Intel E5-2620v3 and E7-4880v2 Message-ID: <20170322061021.GA19156@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 22, 2017 at 01:58:58AM +0000, Cai, Jason wrote: > Dear Kernel Hackers, > > I'm Jason Cai, a kernel developer from Dell EMC. I hit the same issue as the > one Lennart Sorensen sent at Dec 19, 2016. > > I narrow down the issue now. It seems that an unexpected DNA > (Device not Available) may be triggered in the `execve` code path. > Specifically, it exists between `setup_new_exec()` and `start_thread()` in > file `load_elf_binary()`. > > I've added a BUG_ON() just before `start_thread` in `load_elf_binary ` to > assert the fpu status of the current process descriptor should be clean > when performing an exec. It gets triggered and the stack is as the following: As you have a closed kernel module loaded, it's impossible for us to actually tell what you are doing, or support you at all, sorry. Please work with the group that gave you that code, as they are the only ones that can do so. Also, does this happen with 4.10? 3.2 is _really_ old you know. thansk, greg k-h