[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170925131033.2mvlrspgvti5tpbj@wfg-t540p.sh.intel.com>
Date: Mon, 25 Sep 2017 21:10:34 +0800
From: Fengguang Wu <wfg@...ux.intel.com>
To: Ingo Molnar <mingo@...nel.org>, Eric Biggers <ebiggers@...gle.com>
Cc: LKP <lkp@...org>, linux-kernel@...r.kernel.org,
Rik van Riel <riel@...hat.com>,
Kees Cook <keescook@...omium.org>
Subject: Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."):
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
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.
Attached are the dmesg files for 6fc19a42 and its parent commit.
The panic message is,
[ 28.093528] Freeing unused kernel memory: 1656K
[ 28.094182] Write protecting the kernel text: 33872k
[ 28.094922] Write protecting the kernel read-only data: 12160k
[ 28.095441] NX-protecting the kernel data: 23472k
[ 28.130213] init[1] bad frame in sigreturn frame:7fdddcec ip:77f5a1b2 sp:7fdde254 orax:ffffffff in ld-2.15.so[77f59000+20000]
[ 28.131803] init[1] bad frame in sigreturn frame:7fddd62c ip:77f5a1b0 sp:7fdddb94 orax:ffffffff in ld-2.15.so[77f59000+20000]
[ 28.133169] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 28.133169]
[ 28.133979] CPU: 0 PID: 1 Comm: init Not tainted 4.14.0-rc1-00228-g6fc19a4 #1
[ 28.134601] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-20161025_171302-gandalf 04/01/2014
[ 28.135659] Call Trace:
[ 28.136070] dump_stack+0x40/0x5e
[ 28.136594] panic+0x1c5/0x58c
[ 28.137072] forget_original_parent+0x1ee/0x843
[ 28.137514] do_exit+0x1087/0x17c6
[ 28.137813] do_group_exit+0x1d1/0x1d1
[ 28.138220] get_signal+0x1294/0x12ca
[ 28.138546] do_signal+0x2c/0x55b
[ 28.138842] ? force_sig_info+0x1bd/0x1d5
[ 28.139219] ? force_sig+0x22/0x32
[ 28.139519] ? signal_fault+0x14b/0x161
[ 28.139853] ? exit_to_usermode_loop+0x2f/0x2ae
[ 28.140255] ? trace_hardirqs_on_caller+0x2d/0x384
[ 28.140671] exit_to_usermode_loop+0xf7/0x2ae
[ 28.141058] do_int80_syscall_32+0x4e8/0x4fe
[ 28.141432] entry_INT80_32+0x2f/0x2f
[ 28.141829] EIP: 0x77f5a1b0
[ 28.142093] EFLAGS: 00000246 CPU: 0
[ 28.142401] EAX: 00000000 EBX: 0000009c ECX: 00000000 EDX: 00000000
[ 28.142943] ESI: 0000000b EDI: 004ae4c8 EBP: 7fdddce8 ESP: 7fdddb94
[ 28.143482] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 007b
[ 28.143959] Kernel Offset: disabled
Thanks,
Fengguang
View attachment "dmesg-quantal-vp-10:20170925202102:i386-randconfig-b0-09232213:4.14.0-rc1-00228-g6fc19a4:1" of type "text/plain" (88485 bytes)
View attachment "dmesg-quantal-vp-62:20170925203459:i386-randconfig-b0-09232213:4.14.0-rc1-00227-gcc4be4e:1" of type "text/plain" (103984 bytes)
Powered by blists - more mailing lists