From: Kees Cook <keescook@chromium.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Chunyu Hu <chuhu.ncepu@gmail.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [x86/vsyscall] 3dc33bd30f Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Date: Tue, 21 Feb 2017 21:34:53 -0800 [thread overview]
Message-ID: <CAGXu5jLfR=zoxmBMZKOrTKRQV1e+hgqiKWCaDedMs9nNkb39yg@mail.gmail.com> (raw)
In-Reply-To: <CALCETrWpxjKg8VrwKa3nmFVYc6EDBQeENgix0mpz5e_X6xbQig@mail.gmail.com>
On Tue, Feb 21, 2017 at 9:23 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> On Tue, Feb 21, 2017 at 4:46 PM, Kees Cook <keescook@chromium.org> wrote:
>> On Tue, Feb 21, 2017 at 4:39 PM, Chunyu Hu <chuhu.ncepu@gmail.com> wrote:
>>> I hit the similar panic on Fedora 25. Is it the same issue?
>>>
>>>
>>> [ 2.527391] Freeing unused kernel memory: 1688K (ffffffffbdf66000 -
>>> ffffffffbe10c000)
>>> [ 2.535222] Write protecting the kernel read-only data: 14336k
>>> [ 2.542679] Freeing unused kernel memory: 1892K (ffff94cb30827000 -
>>> ffff94cb30a00000)
>>> [ 2.553482] Freeing unused kernel memory: 700K (ffff94cb30d51000 -
>>> ffff94cb30e00000)
>>> [ 2.572048] x86/mm: Checked W+X mappings: passed, no W+X pages found.
>>> Fatal: [ 2.598239] traps: init[1] general protection ip:7fc841bfc642
>>> sp:7ffc3fd85870 error:0no entropy gathering module dete[ 2.606473] in
>>> libc-2.24.so[7fc841bc5000+1bd000]
>>> cted
>>
>> I would not expect a vsyscall table problem if it's truly using glibc
>> 2.24. Maybe something regressed in glibc? That really looks like an
>> attempt to call vsyscalls?
>
> There should be a vsyscall error if so, and shouldn't it be a page
> fault, not a gpf?
Yeah, the earlier email from Fengguang included a vsyscall error, so
I'm not sure what this is, exactly. But if it bisects to the same
commit, we likely need to investigate a bit more.
-Kees
--
Kees Cook
Pixel Security
next prev parent reply other threads:[~2017-02-22 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 5:27 [x86/vsyscall] 3dc33bd30f Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Fengguang Wu
2017-02-21 19:07 ` Kees Cook
[not found] ` <CABATaM7zPdGhqqGtFJ8hGRR6UUk+quWsFwiNY8FO1V2G8O3k3A@mail.gmail.com>
2017-02-22 0:46 ` Kees Cook
2017-02-22 5:23 ` Andy Lutomirski
2017-02-22 5:34 ` Kees Cook [this message]
2017-02-23 14:25 ` Chunyu Hu
2017-02-22 0:49 ` Chunyu Hu
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='CAGXu5jLfR=zoxmBMZKOrTKRQV1e+hgqiKWCaDedMs9nNkb39yg@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=chuhu.ncepu@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=luto@amacapital.net \
--cc=mingo@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).