From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikita Danilov Subject: Re: file struct's dentry being null? Date: Wed, 2 Jul 2003 19:58:12 +0400 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <16131.276.323954.605302@laputa.namesys.com> References: <1057160991.7361.5.camel@zaphod> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from thebsh.namesys.com ([212.16.7.65]:65450 "HELO thebsh.namesys.com") by vger.kernel.org with SMTP id S265059AbTGBPns (ORCPT ); Wed, 2 Jul 2003 11:43:48 -0400 To: Shaya Potter In-Reply-To: <1057160991.7361.5.camel@zaphod> List-Id: linux-fsdevel.vger.kernel.org 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. > if ( !next->dentry ) > printk("file struct: next's dentry is null, %d\n", next); > > and I get a bunch of kernel output along these lines, with 5 different > next memory locations. I only have 3 mount points, so it doesn't seem > to be related to that (though I would have thought it might have been > the list_head on the superblock). anyways, just trying to figure out > what it's pointing to? > > thanks, > > shaya > Nikita. >