On 3/11/16 4:20 PM, Andreas Dilger wrote:
> On Mar 11, 2016, at 10:34 AM, Florian Weimer <fweimer@xxxxxxxxxx> wrote:
>>
>> Is it possible that getdents returns a zero inode number for a name
>> which actually has a file (or directory, device node etc.) behind it?
>
> The d_ino == 0 value is valid to return and means that the filename was
> unlinked from the directory but the entry was not actually removed.
Until recently, didn't the filesystems which use get_next_ino() accept
inode 0 as a legit inode number?
commit 2adc376c551943a07170cbe70f43e6d6065f8906
Author: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
Date: Thu Jun 25 12:25:58 2015 -0300
vfs: avoid creation of inode number 0 in get_next_ino
-Eric
Attachment:
signature.asc
Description: OpenPGP digital signature
