public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Greg KH <greg@kroah.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25-rc2-git4 BUG: sysfs_readdir
Date: Thu, 21 Feb 2008 09:33:22 -0800	[thread overview]
Message-ID: <47BDB5E2.4020101@oracle.com> (raw)
In-Reply-To: <20080221165214.GA30606@kroah.com>

Greg KH wrote:
> On Thu, Feb 21, 2008 at 08:25:53AM -0800, Randy Dunlap wrote:
>> One of my (x86_64) test machines got this on booting 2.6.25-rc2-git4.
>>
>> insmod used greatest stack depth: 4144 bytes left
>> EXT3-fs: INFO: recovery required on readonly filesystem.
>> EXT3-fs: write access will be enabled during recovery.
>> kjournald starting.  Commit interval 5 seconds
>> EXT3-fs: recovery complete.
>> EXT3-fs: mounted filesystem with ordered data mode.
>> modprobe used greatest stack depth: 3600 bytes left
>> BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
>> IP: [<ffffffff802d0f16>] sysfs_readdir+0xe0/0x13f
> 
> That's really wierd, as nothing has changed in this area in a while now.
> did 2.6.25-rc2 work for you ok?

Yes, all previous 2.6.25-versions worked for me.

> Can you enable CONFIG_DEBUG_KOBJECT and see if the kernel log shows you
> what is happening here?  Hm, that's only going to tell you what files
> were created, not what was being read from sysfs...
> 
> How about adding the patch at:
> 	http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/sysfs-crash-debugging.patch
> which has been in -mm for forever that will add the last-accessed sysfs
> file to the oops report.  That might give us more information here.

I'll try those, but I doubt that this is easily reproducible.

-- 
~Randy

      reply	other threads:[~2008-02-21 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 16:25 2.6.25-rc2-git4 BUG: sysfs_readdir Randy Dunlap
2008-02-21 16:35 ` Randy Dunlap
2008-02-21 16:52 ` Greg KH
2008-02-21 17:33   ` Randy Dunlap [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=47BDB5E2.4020101@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox