From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764405AbYBURfB (ORCPT ); Thu, 21 Feb 2008 12:35:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755303AbYBURev (ORCPT ); Thu, 21 Feb 2008 12:34:51 -0500 Received: from rgminet01.oracle.com ([148.87.113.118]:56623 "EHLO rgminet01.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752271AbYBUReu (ORCPT ); Thu, 21 Feb 2008 12:34:50 -0500 Message-ID: <47BDB5E2.4020101@oracle.com> Date: Thu, 21 Feb 2008 09:33:22 -0800 From: Randy Dunlap User-Agent: Thunderbird 1.5.0.5 (X11/20060719) MIME-Version: 1.0 To: Greg KH CC: lkml Subject: Re: 2.6.25-rc2-git4 BUG: sysfs_readdir References: <20080221082553.ddc4e723.randy.dunlap@oracle.com> <20080221165214.GA30606@kroah.com> In-Reply-To: <20080221165214.GA30606@kroah.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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: [] 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