From: Greg KH <gregkh@linuxfoundation.org>
To: "Cai, Jason" <Jason.Cai@dell.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"kernelnewbies@nl.linux.org" <kernelnewbies@nl.linux.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.2: FPU Issue in execve with Intel E5-2620v3 and E7-4880v2
Date: Wed, 22 Mar 2017 07:10:21 +0100 [thread overview]
Message-ID: <20170322061021.GA19156@kroah.com> (raw)
In-Reply-To: <D42483151755344986C41F0DD25FF88D20BDB844@MX206CL03.corp.emc.com>
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
next prev parent reply other threads:[~2017-03-22 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 1:58 Linux 3.2: FPU Issue in execve with Intel E5-2620v3 and E7-4880v2 Cai, Jason
2017-03-22 6:10 ` Greg KH [this message]
2017-03-22 6:19 ` Cai, Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170322061021.GA19156@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason.Cai@dell.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).