All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: jmario@redhat.com
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 15:12:12 +0100	[thread overview]
Message-ID: <5280E5BC.10209@suse.cz> (raw)
In-Reply-To: <5280DB2D.2080202@redhat.com>

On 11.11.2013 14:27, Joe Mario wrote:
> On 11/11/2013 07:07 AM, Michal Marek wrote:
>> 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 just posted the patches.


> 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.

I also did not manage to reproduce it, but then I didn't try too hard.


> Whatever happens, I agree the check in kallsyms.c for kernel symbols
> whose length exceeds the buffer size, needs to be in place.

I plan to merge "[PATCH 2/2] kallsyms: Revert back to 128 max symbol
length" to kbuild.git ASAP, even if "[PATCH 1/2] PCI: Do not use PCI ID
macros in quirk names" is merged later.

Michal

      reply	other threads:[~2013-11-11 14:12 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
2013-11-11 14:12       ` Michal Marek [this message]

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=5280E5BC.10209@suse.cz \
    --to=mmarek@suse.cz \
    --cc=andi@firstfloor.org \
    --cc=fengguang.wu@intel.com \
    --cc=jmario@redhat.com \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.