From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaya Potter Subject: Re: file struct's dentry being null? Date: 02 Jul 2003 12:00:17 -0400 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1057161617.7361.10.camel@zaphod> References: <1057160991.7361.5.camel@zaphod> <16131.276.323954.605302@laputa.namesys.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from opus.cs.columbia.edu ([128.59.20.100]:7834 "EHLO opus.cs.columbia.edu") by vger.kernel.org with ESMTP id S265063AbTGBPtA (ORCPT ); Wed, 2 Jul 2003 11:49:00 -0400 To: Nikita Danilov In-Reply-To: <16131.276.323954.605302@laputa.namesys.com> List-Id: linux-fsdevel.vger.kernel.org On Wed, 2003-07-02 at 11:58, Nikita Danilov wrote: > Shaya Potter writes: > > I decided to do an experiment, in fput, I did a > > > > struct file * next; > > next = (struct file *) file->f_list.next; > > ->f_list.next points to the ->f_list member of next struct file rather > than to the struct file itself. This is how it works for all struct > list_head embedded into objects. yes, I understand that, the idea being that it's the first entry in the struct that you want to link list, so can get the next struct by just dereferencing the list_head (as &list_head == &struct) I was just cheating, but that explains my point, I could see it being null if I hit the real list_head (i.e. on the superblock), but I am getting 5 distinct "hits", with only 3 mount points, so trying to figure out why. the issue I'm trying to figure out is (posted once b4) that I am getting corrupt entries off of ext3's file list in it's superblock, so that when fs_may_remount_ro() is called, it oops with a null pointer exception.