From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: Miklos Szeredi <miklos@szeredi.hu>,
Trond Myklebust <trond.myklebust@primarydata.com>
Cc: "linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 3/3] nfs: Store and use inode in nfs_open_context
Date: Wed, 2 Mar 2016 09:57:24 -0600 [thread overview]
Message-ID: <56D70D64.9010705@suse.de> (raw)
In-Reply-To: <CAJfpegvm_E_K6_wwvuWnnm-D=tBEY=dq_frp8UObUysS4_Pixg@mail.gmail.com>
On 03/02/2016 08:43 AM, Miklos Szeredi wrote:
<snip>
>
>
> 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
next prev parent reply other threads:[~2016-03-02 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 18:12 [PATCH 0/3] Fix overlayfs with NFS as lowerdir Goldwyn Rodrigues
2016-03-01 18:12 ` [PATCH 1/3] ovl: Add d_select_inode to reval dentry operations Goldwyn Rodrigues
2016-03-01 18:12 ` [PATCH 2/3] vfs: Add d_select_inode for overlayfs translation Goldwyn Rodrigues
2016-03-01 18:12 ` [PATCH 3/3] nfs: Store and use inode in nfs_open_context Goldwyn Rodrigues
2016-03-01 20:46 ` Trond Myklebust
2016-03-02 14:27 ` Goldwyn Rodrigues
2016-03-02 14:31 ` Trond Myklebust
2016-03-02 14:38 ` Trond Myklebust
2016-03-02 14:43 ` Miklos Szeredi
2016-03-02 15:57 ` Goldwyn Rodrigues [this message]
2016-03-03 8:16 ` Miklos Szeredi
2016-03-04 10:17 ` Miklos Szeredi
2016-03-04 13:41 ` Trond Myklebust
2016-03-04 14:52 ` Goldwyn Rodrigues
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=56D70D64.9010705@suse.de \
--to=rgoldwyn@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=trond.myklebust@primarydata.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).