Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1739106 > unrolled thread

Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Started byIngo Molnar <mingo@kernel.org>
First post2017-09-25 17:00 +0200
Last post2017-09-26 08:30 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."):  Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Ingo Molnar <mingo@kernel.org> - 2017-09-25 17:00 +0200
    Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."):  Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Fengguang Wu <wfg@linux.intel.com> - 2017-09-26 02:30 +0200
      Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."):  Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Ingo Molnar <mingo@kernel.org> - 2017-09-26 08:30 +0200

#1739106 — Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

FromIngo Molnar <mingo@kernel.org>
Date2017-09-25 17:00 +0200
SubjectRe: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Message-ID<utD1v-7Jk-15@gated-at.bofh.it>
* 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

[toc] | [next] | [standalone]


#1739403

FromFengguang Wu <wfg@linux.intel.com>
Date2017-09-26 02:30 +0200
Message-ID<utLV8-5su-3@gated-at.bofh.it>
In reply to#1739106
On Mon, Sep 25, 2017 at 04:55:09PM +0200, Ingo Molnar wrote:
>
>* 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?

Yes, both of them are free from that crash. :)

Regards,
Fengguang

[toc] | [prev] | [next] | [standalone]


#1739536

FromIngo Molnar <mingo@kernel.org>
Date2017-09-26 08:30 +0200
Message-ID<utRxw-X7-7@gated-at.bofh.it>
In reply to#1739403
* Fengguang Wu <wfg@linux.intel.com> wrote:

> On Mon, Sep 25, 2017 at 04:55:09PM +0200, Ingo Molnar wrote:
> > 
> > * 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?
> 
> Yes, both of them are free from that crash. :)

Great, thanks!

	Ingo

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web