From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [patch 3/7] fs, notify: Add file handle entry into inotify_inode_mark Date: Tue, 13 Nov 2012 14:38:08 -0800 Message-ID: <20121113143808.8d198bfe.akpm@linux-foundation.org> References: <20121112101440.665694060@openvz.org> <20121112101845.839702715@openvz.org> <20121112165540.2ec39f50.akpm@linux-foundation.org> <20121113072057.GC6511@moon> <20121112234001.009b2ae3.akpm@linux-foundation.org> <20121113080032.GF6511@moon> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Al Viro , Alexey Dobriyan , Pavel Emelyanov , James Bottomley , Matthew Helsley , aneesh.kumar@linux.vnet.ibm.com, bfields@fieldses.org To: Cyrill Gorcunov Return-path: In-Reply-To: <20121113080032.GF6511@moon> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, 13 Nov 2012 12:00:32 +0400 Cyrill Gorcunov wrote: > > Dumb question: do we really need inotify_inode_mark.fhandle at all? > > What prevents us from assembling this info on demand when ->show_fdinfo() is > > called? > > exportfs requires the dentry to be passed as an argument while inotify works > with inodes instead and at moment of show-fdinfo the target dentry might be > already deleted but inode yet present as far as I remember. How can the c/r restore code reestablish the inode data if the dentry isn't there any more?