From mboxrd@z Thu Jan  1 00:00:00 1970
From: Shaya Potter <spotter@cs.columbia.edu>
Subject: file struct's dentry being null?
Date: 02 Jul 2003 11:49:51 -0400
Sender: linux-fsdevel-owner@vger.kernel.org
Message-ID: <1057160991.7361.5.camel@zaphod>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from opus.cs.columbia.edu ([128.59.20.100]:21911 "EHLO
	opus.cs.columbia.edu") by vger.kernel.org with ESMTP
	id S265043AbTGBPiW (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Wed, 2 Jul 2003 11:38:22 -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 h62Fqkug009706
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT)
	for <linux-fsdevel@vger.kernel.org>; Wed, 2 Jul 2003 11:52:47 -0400 (EDT)
To: linux-fsdevel@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

I decided to do an experiment, in fput, I did a 

struct file * next;
next = (struct file *) file->f_list.next;
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