Return-Path: Received: from mx2.suse.de ([195.135.220.15]:38686 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754937AbcCBP53 (ORCPT ); Wed, 2 Mar 2016 10:57:29 -0500 Subject: Re: [PATCH 3/3] nfs: Store and use inode in nfs_open_context To: Miklos Szeredi , Trond Myklebust References: <1456855928-29913-1-git-send-email-rgoldwyn@suse.de> <1456855928-29913-4-git-send-email-rgoldwyn@suse.de> <56D6F84B.5040301@suse.de> Cc: "linux-unionfs@vger.kernel.org" , Linux FS-devel Mailing List , Linux NFS Mailing List From: Goldwyn Rodrigues Message-ID: <56D70D64.9010705@suse.de> Date: Wed, 2 Mar 2016 09:57:24 -0600 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: On 03/02/2016 08:43 AM, Miklos Szeredi wrote: > > > Not sure how any dentry seen by NFS became associated with overlayfs. > Through ->f_path by any chance? > Yes, NFS extracts dentry from filp->f_path.dentry in fs/nfs/inode.c nfs_open(). What can it use to evaluate dentry? -- Goldwyn