linux-toradex.git/fs/nfs/callback_proc.c, branch v4.4.26

NFS: Remove unneeded NFS_DEBUG checking before define NFSDBG_FACILITY

2015-10-21T20:49:23+00:00

It's not needed to checking NFS_DEBUG before define NFSDBG_FACILITY, remove it.

Signed-off-by: Kinglong Mee 
Signed-off-by: Trond Myklebust

NFSv4: Add a tracepoint for CB_LAYOUTRECALL

2015-08-25T18:40:06+00:00

Only support for single file layoutrecall for now.

Signed-off-by: Trond Myklebust

NFSv4: Add a tracepoint for CB_GETATTR

2015-08-25T18:40:05+00:00

Signed-off-by: Trond Myklebust

NFS: Remove nfs41_server_notify_{target|highest}_slotid_update()

2015-08-17T18:32:00+00:00

All these functions do is call nfs41_ping_server() without adding
anything.  Let's remove them and give nfs41_ping_server() a better name
instead.

Signed-off-by: Anna Schumaker 
Signed-off-by: Trond Myklebust

NFS: Ensure that we update the sequence id under the slot table lock

2015-06-12T01:15:52+00:00

Fix a callback slot table regression.

Fixes: e937ee714b2d ("nfs: Only update callback sequnce id when CB_SEQUENCE success")
Cc: Kinglong Mee 
Signed-off-by: Trond Myklebust

nfs: Initialize cb_sequenceres information before validate_seqid()

2015-06-12T01:09:06+00:00

For a cb_layoutrecall replay, nfsd got CB_SEQUENCE status of zero,
but all informations of cb_sequenceres are zero too !!!

validate_seqid() return NFS4ERR_RETRY_UNCACHED_REP for a replay,
and skip the initlize cb_sequenceres.

Signed-off-by: Kinglong Mee 
Signed-off-by: Trond Myklebust

nfs: Only update callback sequnce id when CB_SEQUENCE success

2015-06-11T18:00:40+00:00

When testing pnfs layout, nfsd got error NFS4ERR_SEQ_MISORDERED.
It is caused by nfs return NFS4ERR_DELAY before validate_seqid(),
don't update the sequnce id, but nfsd updates the sequnce id !!!

According to RFC5661 20.9.3,
" If CB_SEQUENCE returns an error, then the state of the slot
  (sequence ID, cached reply) MUST NOT change. "

Signed-off-by: Kinglong Mee 
Signed-off-by: Trond Myklebust

NFSv4.1: Don't set up a backchannel if the server didn't agree to do so

2015-02-18T20:30:47+00:00

If the server doesn't agree to out backchannel setup request, then
don't set one up.

Signed-off-by: Trond Myklebust

NFS: fix subtle change in COMMIT behavior

2014-11-24T22:00:42+00:00

Recent work in the pgio layer made it possible for there to be more than one
request per page. This caused a subtle change in commit behavior, because
write.c:nfs_commit_unstable_pages compares the number of *pages* waiting for
writeback against the number of requests on a commit list to choose when to
send a COMMIT in a non-blocking flush.

This is probably hard to hit in normal operation - you have to be using
rsize/wsize < PAGE_SIZE, or pnfs with lots of boundaries that are not page
aligned to have a noticeable change in behavior.

Signed-off-by: Weston Andros Adamson 
Signed-off-by: Trond Myklebust

pnfs: enable CB_NOTIFY_DEVICEID support

2014-09-12T17:33:50+00:00

This code has been around for a while, but never was enabled, although
it is in a working shape.

Note that we implement NOTIFY_DEVICEID4_CHANGE identical to
NOTIFY_DEVICEID4_DELETE.  Given that in either case we can't do anything
but preventing further lookups of a given device ID there isn't much difference
in semantics for the two.  For the delete case the server MUST ensure that
there are no outstanding layouts, while for the change case it doesn't, but
that has little relevance to the client.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Trond Myklebust