From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kyle Sanderson <kyle.leet@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Linux-Kernal <linux-kernel@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel paging request at ffffe8ff7fc00001
Date: Sun, 15 Nov 2015 16:59:57 -0800 [thread overview]
Message-ID: <CA+55aFzTTUYqSWRsiX_XnouKQbXMweLS0JFeyEXe72dWA--1Rw@mail.gmail.com> (raw)
In-Reply-To: <CACsaVZK1cbH+Aq+zG8zNs=wk7jacFTpnwJo8bQvy6L_bd4XLFQ@mail.gmail.com>
On Sun, Nov 15, 2015 at 2:28 PM, Kyle Sanderson <kyle.leet@gmail.com> wrote:
> [] BUG: unable to handle kernel paging request at ffffe8ff7fc00001
> [] IP: [<ffffffff810a174f>] kstat_irqs+0x4f/0x90
> [] CPU: 2 PID: 1078 Comm: usage.pl Not tainted 4.1.7-hardened-r1 #1
> [] Hardware name: Supermicro Super Server/X10SRi-F, BIOS 1.0b 04/21/2015
RSI: 000060f700000001
> [] Call Trace:
> [] [<>] kstat_irqs_usr+0x1e/0x40
> [] [<>] show_stat+0x5ca/0x690
> [] [<>] seq_read+0xcd/0x3b0
> [] [<>] proc_reg_read+0x43/0x70
> [] [<>] __vfs_read+0x23/0xd0
> [] [<>] vfs_read+0xc0/0x1d0
> [] [<>] SyS_read+0x41/0xb0
> [] [<>] system_call_fastpath+0x16/0x72
> [] Code: 83 78 48 00 74 56 4c 8b ...
The code ends up being
mov 0x48(%r13),%rsi
mov __per_cpu_offset(,%rcx,8),%rcx
add (%rsi,%rcx,1),%ebx <-- trapping instruction
which is just the
sum += *per_cpu_ptr(desc->kstat_irqs, cpu);
part of kstat_irqs().
Your registers being
RSI: 000060f700000001
RCX: ffff88087fc00000
and it's RSI that makes no sense - RCX looks like a real kernel
pointer. So it looks like it's the "desc->kstat_irqs" thing that is
for some reason garbage.
I don't see any sane possible reason this would happen, though.
Thomas, does this look like anything you've seen before?
Linus
next prev parent reply other threads:[~2015-11-16 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 22:28 Kyle Sanderson
2015-11-16 0:59 ` Linus Torvalds [this message]
2015-11-16 8:53 ` Thomas Gleixner
[not found] ` <CACsaVZ+1FWY+LEuYYLSLtXhXgF6kb8jbhTgmboJwbE9MK1rubQ@mail.gmail.com>
2015-11-17 5:22 ` Kyle Sanderson
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=CA+55aFzTTUYqSWRsiX_XnouKQbXMweLS0JFeyEXe72dWA--1Rw@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=kyle.leet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®