From: Satya Prakash GS <g.satyaprakash@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: reg. stale post attributes
Date: Thu, 26 May 2016 14:05:29 +0530 [thread overview]
Message-ID: <CAJZK4X4r2WMCqfBsxxswJ95Sznu6TfJk5bBsti_je92ieYnipw@mail.gmail.com> (raw)
Hi,
I have been going through NFS client code and looks like most of the
file operations get post attributes and client applies them after
checking for freshness. How does this scheme work when 2 ops modify
the same attribute on the server ? If op1 and op2 replies come out of
order from server or are applied on server out of order how does the
logic for freshness ensure that the client has the correct attributes.
Sorry, I am not a kernel expert and I could not quote examples for op1
and op2, I am trying to understand the behaviour from the file system
perspective logically.
Thanks,
Satya.
reply other threads:[~2016-05-26 8:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJZK4X4r2WMCqfBsxxswJ95Sznu6TfJk5bBsti_je92ieYnipw@mail.gmail.com \
--to=g.satyaprakash@gmail.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;
as well as URLs for NNTP newsgroup(s).