linux-toradex.git/include/linux/nfs_xdr.h, branch v3.4.91

NFSv4: Ensure we do not reuse open owner names

2012-04-21T03:14:28+00:00

The NFSv4 spec is ambiguous about whether or not it is permissible
to reuse open owner names, so play it safe. This patch adds a timestamp
to the state_owner structure, and combines that with the IDA based
uniquifier.
Fixes a regression whereby the Linux server returns NFS4ERR_BAD_SEQID.

Signed-off-by: Trond Myklebust

NFS: Remove nfs4_setup_sequence from generic rename code

2012-03-21T13:31:46+00:00

This is an NFS v4 specific operation, so it belongs in the NFS v4 code
and not the generic client.

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

NFS: Remove nfs4_setup_sequence from generic unlink code

2012-03-21T13:31:46+00:00

This is an NFS v4 specific operation, so it belongs in the NFS v4 code
and not the generic client.

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

NFS: Remove nfs4_setup_sequence from generic read code

2012-03-21T13:31:45+00:00

This is an NFS v4 specific operation, so it belongs in the NFS v4 code
and not the generic client.

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

NFS: Remove nfs4_setup_sequence from generic write code

2012-03-21T13:31:45+00:00

This is an NFS v4 specific operation, so it belongs in the NFS v4 code
and not the generic client.

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

Merge commit 'nfs-for-3.3-4' into nfs-for-next

2012-03-03T20:05:56+00:00

Conflicts:
	fs/nfs/nfs4proc.c

Back-merge of the upstream kernel in order to fix a conflict with the
slotid type conversion and implementation id patches...

NFS: Request fh_expire_type attribute in "server caps" operation

2012-03-02T22:18:10+00:00

The fh_expire_type file attribute is a filesystem wide attribute that
consists of flags that indicate what characteristics file handles
on this FSID have.

Our client doesn't support volatile file handles.  It should find
out early (say, at mount time) whether the server is going to play
shenanighans with file handles during a migration.

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

NFS: Introduce NFS_ATTR_FATTR_V4_LOCATIONS

2012-03-02T22:18:09+00:00

The Linux NFS client must distinguish between referral events (which
it currently supports) and migration events (which it does not yet
support).

In both types of events, an fs_locations array is returned.  But upper
layers, not the XDR layer, should make the distinction between a
referral and a migration.  There really isn't a way for an XDR decoder
function to distinguish the two, in general.

Slightly adjust the FATTR flags returned by decode_fs_locations()
to set NFS_ATTR_FATTR_V4_LOCATIONS only if a non-empty locations
array was returned from the server.  Then have logic in nfs4proc.c
distinguish whether the locations array is for a referral or
something else.

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

NFSv4: parse and display server implementation ids

2012-03-01T22:10:22+00:00

Shows the implementation ids in /proc/self/mountstats.  This doesn't break
the nfs-utils mountstats tool.

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

NFSv4.1: Convert slotid from u8 to u32

2012-02-15T05:19:43+00:00

It is perfectly legal to negotiate up to 2^32-1 slots in the protocol,
and with 10GigE, we are already seeing that 255 slots is far too limiting.

Signed-off-by: Trond Myklebust