From: Joe Mario <jmario@redhat.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Andi Kleen <andi@firstfloor.org>,
Fengguang Wu <fengguang.wu@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [kallsyms] general protection fault: 0000 [#1] PREEMPT DEBUG_PAGEALLOC
Date: Mon, 11 Nov 2013 08:27:09 -0500 [thread overview]
Message-ID: <5280DB2D.2080202@redhat.com> (raw)
In-Reply-To: <5280C87A.5050606@suse.cz>
On 11/11/2013 07:07 AM, Michal Marek wrote:
> On 10.11.2013 16:23, Andi Kleen wrote:
>> 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.
>
> I'm testing a patch for include/linux/pci.h to use line numbers instead
> of the PCI ID macros to declare the __pci_fixup_* symbols. If that
> works, we can revert the limit back to 128 and only keep the check in
> kallsyms.c.
>
> Michal
Michal:
That would be great.
I found six locations which were still using an array size hardwired to "128" instead of KSYM_NAME_LEN. But none of them were related to the crash Fengguang Wu reported. We built a 32-bit kernel from his config (with a few issues) but were unable to reproduce the crash. Still trying.
Whatever happens, I agree the check in kallsyms.c for kernel symbols whose length exceeds the buffer size, needs to be in place.
Joe
next prev parent reply other threads:[~2013-11-11 13:27 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
2013-11-11 12:07 ` Michal Marek
2013-11-11 13:27 ` Joe Mario [this message]
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=5280DB2D.2080202@redhat.com \
--to=jmario@redhat.com \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.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