kernel.git/fs/nfs/callback_proc.c, branch linux-4.4.y

NFS: Fix bool initialization/comparison

2020-02-14T21:29:59Z

[ Upstream commit 6089dd0d731028531fb1148be9fd33274ff90da4 ] Bool initializations should use true and false. Bool tests don't need comparisons. Signed-off-by: Thomas Meyer Signed-off-by: Anna Schumaker Signed-off-by: Sasha Levin

NFS: Remove unneeded NFS_DEBUG checking before define NFSDBG_FACILITY

2015-10-21T20:49:23Z

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:06Z

Only support for single file layoutrecall for now. Signed-off-by: Trond Myklebust

NFSv4: Add a tracepoint for CB_GETATTR

2015-08-25T18:40:05Z

Signed-off-by: Trond Myklebust

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

2015-08-17T18:32:00Z

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:52Z

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:06Z

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:40Z

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:47Z

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:42Z

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