From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Simon Kirby <sim@hostway.ca>
Cc: linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@suse.de>,
mark gross <markgross@thegnar.org>, Takashi Iwai <tiwai@suse.de>
Subject: Re: [linux-pm] [2.6.36-rc4/HEAD] unable to handle kernel NULL pointer dereference?(plist_add)
Date: Thu, 16 Sep 2010 20:26:16 +0200 [thread overview]
Message-ID: <201009162026.17003.rjw@sisk.pl> (raw)
In-Reply-To: <20100915234633.GW23979@hostway.ca>
On Thursday, September 16, 2010, Simon Kirby wrote:
> On Tue, Sep 14, 2010 at 10:38:25PM +0200, Rafael J. Wysocki wrote:
>
> > Hmm, interesting. This looks like a plist corruption to me, but can you please
> > check (using gdb) what line of code corresponds to the address
> > plist_add+0x36/0xa0 ?
>
> I ended up rebuilding since then, and I enabled a bunch of debugging
> stuff. Does this help make it more obvious? I'll try your other patch
> tonight, but I still don't get what's wrong with the existing code.
That's not necessary, since the https://bugzilla.kernel.org/show_bug.cgi?id=17922
patch works for you.
Thanks,
Rafael
prev parent reply other threads:[~2010-09-16 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 7:00 [2.6.36-rc4/HEAD] unable to handle kernel NULL pointer dereference (plist_add) Simon Kirby
2010-09-14 20:38 ` [linux-pm] " Rafael J. Wysocki
2010-09-14 22:06 ` Rafael J. Wysocki
2010-09-15 8:29 ` Takashi Iwai
2010-09-15 13:05 ` mark gross
2010-09-15 13:12 ` Takashi Iwai
2010-09-15 13:17 ` mark gross
2010-09-16 0:23 ` Simon Kirby
2010-09-16 2:52 ` mark gross
2010-09-15 23:46 ` [linux-pm] [2.6.36-rc4/HEAD] unable to handle kernel NULL pointer dereference?(plist_add) Simon Kirby
2010-09-16 18:26 ` Rafael J. Wysocki [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=201009162026.17003.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=James.Bottomley@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=sim@hostway.ca \
--cc=tiwai@suse.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®