From: Ingo Molnar <mingo@kernel.org>
To: kernel test robot <fengguang.wu@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>,
wfg@linux.intel.com, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Date: Sun, 24 Sep 2017 13:11:17 +0200 [thread overview]
Message-ID: <20170924111117.7nftqa2g5lnzn7xr@gmail.com> (raw)
In-Reply-To: <59c6e23f.nOk6ceVoId2JVMIx%fengguang.wu@intel.com>
* kernel test robot <fengguang.wu@intel.com> wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/fpu
>
> commit 9f4835fb965d8eea7e608d0cb62c246c804dec90
> Author: Eric Biggers <ebiggers@google.com>
> AuthorDate: Fri Sep 22 10:41:55 2017 -0700
> Commit: Ingo Molnar <mingo@kernel.org>
> CommitDate: Sat Sep 23 11:02:00 2017 +0200
>
> x86/fpu: Tighten validation of user-supplied xstate_header
Would it be possible to re-start this bisection, now that I've split up the commit
into 10 more obvious patches?
My guess is that it's one of these two that is the bad commit:
3deb4cca945b: x86/fpu: Copy the full header in copy_user_to_xstate()
cfbd048cce44: x86/fpu: Copy the full state_header in copy_kernel_to_xstate()
... but it could be some of the others as well.
Thanks,
Ingo
next prev parent reply other threads:[~2017-09-24 11:11 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 [this message]
2017-09-25 2:20 ` kernel test robot
2017-09-25 13:10 ` Fengguang Wu
2017-09-25 14:55 ` Ingo Molnar
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=20170924111117.7nftqa2g5lnzn7xr@gmail.com \
--to=mingo@kernel.org \
--cc=ebiggers@google.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--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