Re: inode values in file system driver

[Andreas Schwab <schwab@suse.de>]

Nikita Danilov <Nikita@Namesys.COM> writes:

|> Andreas Schwab writes:
|>  > Erik Mouw <J.A.K.Mouw@its.tudelft.nl> writes:
|>  > 
|>  > |> On Sat, May 10, 2003 at 09:18:20PM +0100, Adrian McMenamin wrote:
|>  > |> > Am I allowed to assign the value 0 to an inode in a file system driver? I seem 
|>  > |> > to be having problems with a file that is being assigned this inode value 
|>  > |> > (its a FAT based filesystem so the inode values are totally artificial).
|>  > |> 
|>  > |> Yes, you are. However, glibc thinks that inode 0 is special and won't
|>  > |> show it.
|>  > 
|>  > BS. This has nothing at all to do with glibc.
|> 
|> from glibc-2.2.4/sysdeps/unix/readdir.c:
|> 
|>       /* Skip deleted files.  */
|>     } while (dp->d_ino == 0);
|> 
|> In other words, readdir(3) will not return dirent for inode with ino 0.

I stand corrected.  I was thinking of getdirentries, which does not have
this problem.  But this is traditional Unix behaviour.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."