+Bruce, +Jeff... On Wed, Sep 9, 2015 at 1:12 PM, Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> wrote: > On Wed, Sep 9, 2015 at 9:37 AM, Andrew W Elble <aweits@xxxxxxx> wrote: >> >> In attempting to troubleshoot other issues, we've run into this race >> with 4.1.4 (both client and server) with a few cherry-picked patches >> from upstream. This is my attempt at a redacted packet-capture. >> >> These all affect the same fh/stateid: >> >> 116 -> OPEN (will be an upgrade / for write) >> 117 -> OPEN_DOWNGRADE (to read for the existing stateid / seqid = 0x6 >> >> 121 -> OPEN_DOWNGRADE (completed last / seqid = 0x8) >> 122 -> OPEN (completed first / seqid = 0x7) >> >> Attempts to write using that stateid fail because the stateid doesn't >> have write access. >> >> Any thoughts? I can share more data from the capture if needed. > > Bruce & Jeff, > > Given that the client sent a non-zero seqid, why is the OPEN_DOWNGRADE > being executed after the OPEN here? Surely, if that is the case, the > server should be returning NFS4ERR_OLD_STATEID and failing the > OPEN_DOWNGRADE operation? > > Cheers > Trond -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
