From: Ingo Molnar <mingo@kernel.org>
To: Fengguang Wu <wfg@linux.intel.com>
Cc: Eric Biggers <ebiggers@google.com>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Date: Mon, 25 Sep 2017 16:55:09 +0200 [thread overview]
Message-ID: <20170925145509.py4prxskkbpqfjsd@gmail.com> (raw)
In-Reply-To: <20170925131033.2mvlrspgvti5tpbj@wfg-t540p.sh.intel.com>
* Fengguang Wu <wfg@linux.intel.com> wrote:
> On Mon, Sep 25, 2017 at 10:20:13AM +0800, kernel test robot wrote:
> > Hi Ingo,
> >
> > On your request I'm resending the report here, with attached dmesg,
> > kconfig and reproduce script.
> >
> > I'll go on to test your split up commits, too.
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/fpu
>
> It looks 6fc19a42 ("x86/fpu: Use validate_xstate_header() to validate
> the xstate_header in sanitize_restored_xstate()") is the first bad commit.
Thank you! Could you check that the latest tip:master or tip:WIP.x86/fpu
(9cff7344187e) fixes this crash?
Thanks,
Ingo
next prev parent reply other threads:[~2017-09-25 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 22:37 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b kernel test robot
2017-09-24 10:00 ` Ingo Molnar
2017-09-24 11:11 ` Ingo Molnar
2017-09-25 2:20 ` kernel test robot
2017-09-25 13:10 ` Fengguang Wu
2017-09-25 14:55 ` Ingo Molnar [this message]
2017-09-26 0:19 ` Fengguang Wu
2017-09-26 6:25 ` Ingo Molnar
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=20170925145509.py4prxskkbpqfjsd@gmail.com \
--to=mingo@kernel.org \
--cc=ebiggers@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=riel@redhat.com \
--cc=wfg@linux.intel.com \
/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