From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vivek Goyal Subject: Re: [PATCH v2 00/11] overlayfs constant inode numbers Date: Tue, 25 Apr 2017 07:52:57 -0400 Message-ID: <20170425115257.GA11500@redhat.com> References: <1493025256-27188-1-git-send-email-amir73il@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42450 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1176064AbdDYLw7 (ORCPT ); Tue, 25 Apr 2017 07:52:59 -0400 Content-Disposition: inline In-Reply-To: <1493025256-27188-1-git-send-email-amir73il@gmail.com> Sender: linux-unionfs-owner@vger.kernel.org List-Id: linux-unionfs@vger.kernel.org To: Amir Goldstein Cc: Miklos Szeredi , Al Viro , linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org On Mon, Apr 24, 2017 at 12:14:05PM +0300, Amir Goldstein wrote: > Miklos, > > Following your comments on the 'stable inodes' series from last week, > this series fixes constant inode numbers for stat(2) with any layer > configuration. > > For the case of all *lower* layers on same fs that supports NFS export, > redirect by file handle will be used to optimize the lookup of the copy > up origin of non-dir inode. > > For the case of *all* layers on same fs, overlayfs also gains: > - Persistent inode numbers for directories > - Correct results for du -x > > Consistcy of stat(2) st_ino with readdir(3) d_ino is NOT addressed by > this series. It will be addressed for the 'samefs' configuration by the > follow up 'stable inode' work, which is also going to address preserving > hardlinks on copy up. Hi Amir, We need to update Documentation/filesystems/overlayfs.txt as well to reflect new semantics of reporting st_dev and st_ino? Vivek