From: Greg KH <gregkh@suse.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org, Chris Rankin <rankincj@yahoo.com>
Subject: Re: [BUG] Linux 2.6.20.2 - unable to handle kernel paging request - still accessing freed memory
Date: Thu, 15 Mar 2007 15:27:07 -0700 [thread overview]
Message-ID: <20070315222707.GI31713@suse.de> (raw)
In-Reply-To: <84144f020703140423h2562a353g40c156584943bb7@mail.gmail.com>
On Wed, Mar 14, 2007 at 01:23:02PM +0200, Pekka Enberg wrote:
> Hi Greg,
>
> I think there's some sort of reference counting problem with sysfs in
> 2.6.20 kernels. Can you please help us debug it further?
Is there any way you can use 'git bisect' to try to track down the root
cause of this?
thanks,
greg k-h
next prev parent reply other threads:[~2007-03-15 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-10 14:09 [BUG] Linux 2.6.20.2 - unable to handle kernel paging request - still accessing freed memory Chris Rankin
2007-03-14 11:18 ` Pekka Enberg
2007-03-14 11:23 ` Pekka Enberg
2007-03-15 22:27 ` Greg KH [this message]
2007-03-16 7:23 ` Pekka Enberg
2007-03-16 8:31 ` Chris Rankin
2007-03-16 10:25 ` Pekka Enberg
2007-03-16 11:30 ` Chris Rankin
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=20070315222707.GI31713@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rankincj@yahoo.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