Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"bcodding@redhat.com" <bcodding@redhat.com>
Subject: Re: client lookup_revalidate bug
Date: Wed, 29 May 2019 16:21:56 +0000	[thread overview]
Message-ID: <458733948202ed0fddf37cbb79730b5ebdabd551.camel@hammerspace.com> (raw)
In-Reply-To: <D4DAB8F2-CAA7-4BC3-B0A0-4EAF5E9DE261@redhat.com>

On Wed, 2019-05-29 at 11:08 -0400, Benjamin Coddington wrote:
> Hey, here's an interesting one, this seems wrong:
> 
> [root@fedora27_c2_v5 ~]# mkdir /mnt/one
> [root@fedora27_c2_v5 ~]# mkdir /mnt/two
> [root@fedora27_c2_v5 ~]# mount -t nfs -ov4,noac,sec=sys,nosharecache 
> 192.168.122.50:/exports /mnt/one
> [root@fedora27_c2_v5 ~]# mount -t nfs -ov4,noac,sec=sys,nosharecache 
> 192.168.122.50:/exports /mnt/two
> [root@fedora27_c2_v5 ~]# mkdir /mnt/one/A
> [root@fedora27_c2_v5 ~]# mkdir /mnt/one/B
> [root@fedora27_c2_v5 ~]# touch /mnt/one/A/foo
> [root@fedora27_c2_v5 ~]# cat /mnt/two/A/foo
> [root@fedora27_c2_v5 ~]# mv /mnt/two/A/foo /mnt/two/B/foo
> [root@fedora27_c2_v5 ~]# mv /mnt/one/B/foo /mnt/one/A/foo
> [root@fedora27_c2_v5 ~]# cat /mnt/two/A/foo
> [root@fedora27_c2_v5 ~]# stat /mnt/two/B/foo
>    File: /mnt/two/B/foo
>    Size: 0         	Blocks: 0          IO Block: 262144 regular
> empty 
> file
> Device: 2fh/47d	Inode: 439603      Links: 1
> Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid:
> (    0/    root)
> Context: system_u:object_r:nfs_t:s0
> Access: 2019-05-28 14:00:18.929663705 -0400
> Modify: 2019-05-28 14:00:18.929663705 -0400
> Change: 2019-05-28 14:00:58.990124573 -0400
>   Birth: -
> 
> 
> ^^ that lstat should return -ENOENT.
> 
> I think we detect a stale directory by comparing the directory's 
> change_attr with the dentry's d_time.  But, here's a case where they
> are 
> the same!
> 
> Am I wrong about this, or any clever ideas to catch this case?
> 

When you are mounting using 'nosharecache' then you are making /mnt/one
and /mnt/two act as if they are different filesystems. The fact that
they are the same on the server, means you are setting up a testcase
where the files+directories are acting like the "changing on the
server" case as far as the client is concerned.

If you want the above to work in a sane fashion, then just don't use
'nosharecache'.

Cheers
   Trond

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2019-05-29 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 15:08 client lookup_revalidate bug Benjamin Coddington
2019-05-29 16:21 ` Trond Myklebust [this message]
2019-05-29 16:39   ` Benjamin Coddington
2019-05-29 17:02     ` Achilles Gaikwad
2019-05-29 17:19     ` Trond Myklebust
2019-05-30 10:35       ` Benjamin Coddington
2019-05-30 13:44         ` Benjamin Coddington

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=458733948202ed0fddf37cbb79730b5ebdabd551.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=bcodding@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    /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