[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOQ4uxgrcJxYN86zMFYU7zVofwTihJ_RkNW+1mkdS9C3zQxamQ@mail.gmail.com>
Date: Wed, 30 Nov 2016 18:36:18 +0200
From: Amir Goldstein <amir73il@...il.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: "linux-unionfs@...r.kernel.org" <linux-unionfs@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [POC/RFC PATCH] overlayfs: constant inode numbers
On Wed, Nov 30, 2016 at 5:05 PM, Amir Goldstein <amir73il@...il.com> wrote:
...
> For non-lowets entry, we can provide mount option 'readdir_ino'.
> With readdir_ino, readdir pays a penalty of getxattr for any non-lowest
> entry (either OVL_XATTR_FH or OVL_XATTR_INO).
> Without readdir_ino, readdir will get d_ino = 0, in which case, at least
> `find <path> --inum=<n>` does the right thing (fallback to fstat for
> this dirent).
>
Well, I was wrong about findutils. The -inum filter seems to fail to find
the file if d_ino is set to 0.
That's at least the case for findutils 4.4.2 that I have on debian and
4.7.0-git that I built myself.
Now I have a simple command line to use for the xfstest...
Amir.
Powered by blists - more mailing lists