From: Andi Kleen <andi@firstfloor.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Joe Mario <jmario@redhat.com>, Michal Marek <mmarek@suse.cz>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org
Subject: Re: [kallsyms] general protection fault: 0000 [#1] PREEMPT DEBUG_PAGEALLOC
Date: Sun, 10 Nov 2013 16:23:38 +0100 [thread overview]
Message-ID: <20131110152338.GN29695@two.firstfloor.org> (raw)
In-Reply-To: <20131110094005.GA21916@localhost>
On Sun, Nov 10, 2013 at 05:40:05PM +0800, Fengguang Wu wrote:
> Hi Joe,
>
> FYI. Here is another bisect result.
I bet it's that strncpy() in kallsyms.c and someone passing in a too
short buffer on a 32bit kernel.
We should really kill strncpy(), it's just evil.
-And
next prev parent reply other threads:[~2013-11-10 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 9:40 [kallsyms] general protection fault: 0000 [#1] PREEMPT DEBUG_PAGEALLOC Fengguang Wu
2013-11-10 15:23 ` Andi Kleen [this message]
2013-11-11 12:07 ` Michal Marek
2013-11-11 13:27 ` Joe Mario
2013-11-11 14:12 ` Michal Marek
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=20131110152338.GN29695@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=jmario@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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