From: Eric Sandeen <sandeen@sandeen.net>
To: Andreas Dilger <adilger@dilger.ca>, Florian Weimer <fweimer@redhat.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: Can getdents return zero inode numbers?
Date: Tue, 19 Apr 2016 16:48:00 -0400 [thread overview]
Message-ID: <57169980.50803@sandeen.net> (raw)
In-Reply-To: <14BE767D-13C2-4946-B8C7-042654875E05@dilger.ca>
[-- Attachment #1.1: Type: text/plain, Size: 742 bytes --]
On 3/11/16 4:20 PM, Andreas Dilger wrote:
> On Mar 11, 2016, at 10:34 AM, Florian Weimer <fweimer@redhat.com> 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@redhat.com>
Date: Thu Jun 25 12:25:58 2015 -0300
vfs: avoid creation of inode number 0 in get_next_ino
-Eric
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 881 bytes --]
next prev parent reply other threads:[~2016-04-19 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 17:34 Can getdents return zero inode numbers? Florian Weimer
2016-03-11 21:20 ` Andreas Dilger
2016-03-11 21:39 ` Florian Weimer
2016-04-08 19:40 ` Florian Weimer
2016-04-10 21:30 ` Andreas Dilger
2016-04-19 20:48 ` Eric Sandeen [this message]
2016-04-20 1:46 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57169980.50803@sandeen.net \
--to=sandeen@sandeen.net \
--cc=adilger@dilger.ca \
--cc=fweimer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.