From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:38882 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751522AbcDHTkN (ORCPT ); Fri, 8 Apr 2016 15:40:13 -0400 Subject: Re: Can getdents return zero inode numbers? To: Andreas Dilger References: <56E301BC.9090405@redhat.com> <14BE767D-13C2-4946-B8C7-042654875E05@dilger.ca> Cc: Linux FS Devel From: Florian Weimer Message-ID: <57080919.6000101@redhat.com> Date: Fri, 8 Apr 2016 21:40:09 +0200 MIME-Version: 1.0 In-Reply-To: <14BE767D-13C2-4946-B8C7-042654875E05@dilger.ca> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 03/11/2016 10:20 PM, Andreas Dilger wrote: > On Mar 11, 2016, at 10:34 AM, Florian Weimer > 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. Thanks. Which file systems do this? Is it possible to see this in action? Florian