From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaya Potter Subject: oops in fs_may_remount_ro() Date: 25 Jun 2003 16:57:23 -0400 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1056574643.1094.8.camel@zaphod> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from opus.cs.columbia.edu ([128.59.20.100]:63675 "EHLO opus.cs.columbia.edu") by vger.kernel.org with ESMTP id S265072AbTFYUp3 (ORCPT ); Wed, 25 Jun 2003 16:45:29 -0400 Received: from DYN249418YKT.watson.ibm.com (yktgi01e0-s1.watson.ibm.com [129.34.20.16]) (authenticated bits=0) by opus.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id h5PKxeug007868 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 25 Jun 2003 16:59:41 -0400 (EDT) To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org I'm somehow causing an oops in fs_may_remount_ro() (triggered by rebooting when it tries to remount / ) in that the list of files off the superblock either points to an invalid entry of some sort. It's either invalid because the dentry is null, or because it doesn't exist evidence seems to point in the not existent direction, as I stuck in an if (!dentry) { printk("bad dentry\n"); continue; } in the loop, and it went nuts printing out data. I dont know enough about this, so trying to figure out what could cause this problem? The only things I modify are tty device related, so shouldn't have any affect on the ext3 root (well seen w/ both an ext3 based /dev and a devfs based dev) anyways, any help/ideas/pointers would be appreciated. thanks, shaya