linux.git/fs/nfs/callback_proc.c, branch v4.0

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

pnfs: add return_range method

2014-09-10T19:47:03+00:00

If a layout driver keeps per-inode state outside of the layout segments it
needs to be notified of any layout returns or recalls on an inode, and not
just about the freeing of layout segments.  Add a method to acomplish this,
which will allow the block layout driver to handle the case of truncated
and re-expanded files properly.

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

pnfs: force a layout commit when encountering busy segments during recall

2014-09-10T19:47:02+00:00

Expedite layout recall processing by forcing a layout commit when
we see busy segments.  Without it the layout recall might have to wait
until the VM decided to start writeback for the file, which can introduce
long delays.

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

NFSv4.1: Minor optimisation in get_layout_by_fh_locked()

2014-02-20T02:21:06+00:00

If the filehandles match, but the igrab() fails, or the layout is
freed before we can get it, then just return NULL.

Signed-off-by: Trond Myklebust

NFSv4.1: Ensure that the layout recall callback matches layout stateids

2014-02-20T02:21:05+00:00

It is not sufficient to compare filehandles when we receive a layout
recall from the server; we also need to check that the layout stateids
match.

Reported-by: shaobingqing 
Signed-off-by: Trond Myklebust

NFS: When displaying session slot numbers, use "%u" consistently

2013-09-03T19:26:30+00:00

Clean up, since slot and sequence numbers are all unsigned anyway.

Among other things, squelch compiler warnings:

linux/fs/nfs/nfs4proc.c: In function ‘nfs4_setup_sequence’:
linux/fs/nfs/nfs4proc.c:703:2: warning: signed and unsigned type in
	conditional expression [-Wsign-compare]

and

linux/fs/nfs/nfs4session.c: In function ‘nfs4_alloc_slot’:
linux/fs/nfs/nfs4session.c:151:31: warning: signed and unsigned type in
	conditional expression [-Wsign-compare]

Signed-off-by: Chuck Lever 
Signed-off-by: Trond Myklebust

NFSv4.1: Add tracepoints for debugging slot table operations

2013-08-22T12:58:27+00:00

Add tracepoints to nfs41_setup_sequence and nfs41_sequence_done
to track session and slot table state changes.

Signed-off-by: Trond Myklebust

NFSv4: Add tracepoints for debugging delegations

2013-08-22T12:58:24+00:00

Set up tracepoints to track when delegations are set, reclaimed,
returned by the client, or recalled by the server.

Signed-off-by: Trond Myklebust