public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Roi Azarzar <roi.azarzar@vastdata.com>, linux-nfs@vger.kernel.org
Cc: Sagi Grimberg <sagi.grimberg@vastdata.com>
Subject: Re: NFS4 Delegations: Unexpected behavior of readdir + child delegations
Date: Thu, 26 Dec 2024 17:08:35 -0500	[thread overview]
Message-ID: <cb543edfa32394804bd868064b9e501d6a4634df.camel@kernel.org> (raw)
In-Reply-To: <CAF3mN6V7zDoGxx5Gufd=BJR_4_hOeyx+OfgNk-G0sAmwOxMjAw@mail.gmail.com>

On Thu, 2024-12-26 at 08:56 +0200, Roi Azarzar wrote:
> Hi,
> 
> I Tested the following against linux server:
> 1. client 1:
> > 
> > > > > open1 = os.open("/mnt/roi_test/var/nfs/export_top/test_for_readdir_deleg/file1.txt",os.O_RDWR)
> > 
> > > > > open2 = os.open("/mnt/roi_test/var/nfs/export_top/test_for_readdir_deleg/file2.txt",os.O_RDWR)
> > 
> > > > > open3 = os.open("/mnt/roi_test/var/nfs/export_top/test_for_readdir_deleg/file3.txt",os.O_RDWR)
> 
> 
> 2. client 2:
> [centos@rnd-nfs-c01 ~]$ stat
> /mnt/roi_test/var/nfs/export_top/test_for_readdir_deleg/ File:
> '/mnt/roi_test/var/nfs/export_top/test_for_readdir_deleg/' Size: 57
> Blocks: 0 IO Block: 1048576 directory Device: 2fh/47d Inode: 33564533
> Links: 2 Access: (0777/drwxrwxrwx) Uid: ( 1000/ centos) Gid: ( 1000/
> centos) Access: 2024-12-25 21:51:41.103296943 +0200 Modify: 2024-12-25
> 21:51:40.160278216 +0200 Change: 2024-12-25 21:52:05.733786050 +0200
> Birth: - [centos@rnd-nfs-c01 ~]$ ls -ltr
> /mnt/roi_test/var/nfs/export_top/test_for_readdir_deleg/ total 0
> -rwxrwxrwx 1 centos centos 0 Dec 25 21:51 file2.txt -rwxrwxrwx 1
> centos centos 0 Dec 25 21:51 file1.txt
> -rwxrwxrwx 1 centos centos 0 Dec 25 22:06 file3.txt
> 
> I noticed in the pcap that the server doesn't wait for all CB_GETATTR
> responses for all childs before responding on READDIR, and for some
> reason also sends CB_RECALL.
> 
> 
> Any reason why to do so?
> 
> Linux version:
> Linux protocol-linux-server 6.10.3-custom #1 SMP PREEMPT_DYNAMIC Mon
> Aug 12 12:42:22 IDT 2024 x86_64 x86_64 x86_64 GNU/Linux

There are some known bugs in the server's CB_GETATTR implementation
that were fixed recently (bf92e5008b17f9, in particular). Are you able
to test a v6.13-rc client? Does it show similar behavior?

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2024-12-26 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26  6:56 NFS4 Delegations: Unexpected behavior of readdir + child delegations Roi Azarzar
2024-12-26 22:08 ` Jeff Layton [this message]

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=cb543edfa32394804bd868064b9e501d6a4634df.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=roi.azarzar@vastdata.com \
    --cc=sagi.grimberg@vastdata.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