From: Sachin Prabhu <sprabhu@redhat.com>
To: linux-nfs@vger.kernel.org
Subject: stateid sequence numbers
Date: Wed, 01 Feb 2012 17:30:20 +0000 [thread overview]
Message-ID: <1328117421.17411.15.camel@sprabhu.fab.redhat.com> (raw)
Is there any reason we need to treat the stateid as an opaque object in
NFSv4?
The RFC states the following
--
RFC 3530 - Page 23
stateid4
struct stateid4 {
uint32_t seqid;
opaque other[12];
};
This structure is used for the various state sharing mechanisms
between the client and server. For the client, this data structure
is read-only. The starting value of the seqid field is undefined.
The server is required to increment the seqid field monotonically at
each transition of the stateid. This is important since the client
will inspect the seqid in OPEN stateids to determine the order of
OPEN processing done by the server.
--
We have a user report a problem for which we believe we need to check
the version of the stateid by taking a look at the sequence id reported
for that state. Is there a good reason why this should be opaque?
Sachin Prabhu
reply other threads:[~2012-02-01 19:26 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=1328117421.17411.15.camel@sprabhu.fab.redhat.com \
--to=sprabhu@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;
as well as URLs for NNTP newsgroup(s).