I've been testing these a bit, I think this was causing an issue...
Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> writes:
> diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
> index d615b7cdfa8f..752b18e88266 100644
> --- a/fs/nfs/nfs4state.c
> +++ b/fs/nfs/nfs4state.c
> @@ -986,6 +986,22 @@ static int nfs4_copy_lock_stateid(nfs4_stateid *dst,
> return ret;
> }
>
> +bool nfs4_refresh_open_stateid(nfs4_stateid *dst, struct nfs4_state *state)
> +{
> + bool ret;
> + int seq;
> +
> + do {
> + ret = false;
> + seq = read_seqbegin(&state->seqlock);
> + if (nfs4_state_match_open_stateid_other(state, dst)) {
> + dst->seqid = state->stateid.seqid;
You mean:
dst->seqid = state->open_stateid.seqid;
?
> + ret = true;
> + }
> + } while (read_seqretry(&state->seqlock, seq));
> + return ret;
> +}
> +
> static void nfs4_copy_open_stateid(nfs4_stateid *dst, struct nfs4_state *state)
> {
> const nfs4_stateid *src;
Thanks,
Andy
--
Andrew W. Elble
aweits@xxxxxxxxxxxxxxxxxx
Infrastructure Engineer, Communications Technical Lead
Rochester Institute of Technology
PGP: BFAD 8461 4CCF DC95 DA2C B0EB 965B 082E 863E C912
--
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
