From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Zdenek Kabelac <zkabelac@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Crash of 3.12-rc2 BUG: unable to handle kernel NULL pointer dereference
Date: Fri, 27 Sep 2013 22:05:05 +0100 [thread overview]
Message-ID: <20130927210505.GM12758@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAErSpo74E-EKJN16A44UEGraZ9NE09a5q2_zQrkMuOANtQx0rQ@mail.gmail.com>
On Fri, Sep 27, 2013 at 10:04:44AM -0600, Bjorn Helgaas wrote:
> [+cc Thomas, Russell]
Someone is doing something quite bad in the kernel, and as yet I've not
figured out a way to track it down.
The issue is this: someone is kfree'ing a kobject before its release
function has been called, and the memory is being re-used. The problem
is that when the last reference has been dropped with the debug enabled,
the kobject is linked into the timer lists for the delayed work. When
the timer lists get run, they're found to be corrupted.
The obvious solution to this is to move the delayed work out of the
kobject into a separately allocated structure. That would work if
x86 didn't register kobjects very early in boot, before the memory
allocators were up and running.
Frankly, I've no idea how to solve this. So I regard x86 as just being
difficult and broken. :)
If anyone has any ideas, then I'm all ears.
http://www.annhuey.com/ed-pix/fa_i-pix/I%27m-All-Ears.jpg
prev parent reply other threads:[~2013-09-27 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 11:57 Zdenek Kabelac
2013-09-27 13:13 ` Zdenek Kabelac
2013-09-27 16:04 ` Bjorn Helgaas
2013-09-27 21:05 ` Russell King - ARM Linux [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=20130927210505.GM12758@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zkabelac@redhat.com \
/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®