linux-toradex.git/include/linux/sunrpc/xdr.h, branch v3.10.2

sunrpc: trim off trailing checksum before returning decrypted or integrity authenticated buffer

2013-02-08T20:19:10+00:00

When GSSAPI integrity signatures are in use, or when we're using GSSAPI
privacy with the v2 token format, there is a trailing checksum on the
xdr_buf that is returned.

It's checked during the authentication stage, and afterward nothing
cares about it. Ordinarily, it's not a problem since the XDR code
generally ignores it, but it will be when we try to compute a checksum
over the buffer to help prevent XID collisions in the duplicate reply
cache.

Fix the code to trim off the checksums after verifying them. Note that
in unwrap_integ_data, we must avoid trying to reverify the checksum if
the request was deferred since it will no longer be present when it's
revisited.

Signed-off-by: Jeff Layton

sunrpc: fix comment in struct xdr_buf definition

2013-02-05T14:41:14+00:00

...these pages aren't necessarily contiguous.

Signed-off-by: Jeff Layton 
Signed-off-by: J. Bruce Fields

SUNRPC: Remove unused function xdr_encode_pages

2012-06-28T21:20:49+00:00

Signed-off-by: Trond Myklebust

SUNRPC: Add the helper xdr_stream_pos

2012-06-28T21:20:44+00:00

Add a helper to report the current offset from the start of the
xdr_stream.

Signed-off-by: Trond Myklebust

SUNRPC: xdr_read_pages should return the amount of XDR encoded page data

2012-06-28T21:20:43+00:00

Callers of xdr_read_pages() will want to know exactly how much XDR
data is encoded in the pages after the data realignment.

Signed-off-by: Trond Myklebust

SUNRPC: Don't decode beyond the end of the RPC reply message

2012-06-28T21:20:41+00:00

Now that xdr_inline_decode() will automatically cross into the page
buffers, we need to ensure that it doesn't exceed the total reply
message length.

This patch sets up a counter that tracks the number of words
remaining in the reply message, and ensures that xdr_inline_decode,
xdr_read_pages and xdr_enter_page respect the end of message boundary.

Signed-off-by: Trond Myklebust

NFSv4: include bitmap in nfsv4 get acl data

2012-01-05T15:42:42+00:00

The NFSv4 bitmap size is unbounded: a server can return an arbitrary
sized bitmap in an FATTR4_WORD0_ACL request.  Replace using the
nfs4_fattr_bitmap_maxsz as a guess to the maximum bitmask returned by a server
with the inclusion of the bitmap (xdr length plus bitmasks) and the acl data
xdr length to the (cached) acl page data.

This is a general solution to commit e5012d1f "NFSv4.1: update
nfs4_fattr_bitmap_maxsz" and fixes hitting a BUG_ON in xdr_shrink_bufhead
when getting ACLs.

Fix a bug in decode_getacl that returned -EINVAL on ACLs > page when getxattr
was called with a NULL buffer, preventing ACL > PAGE_SIZE from being retrieved.

Cc: stable@kernel.org
Signed-off-by: Andy Adamson 
Signed-off-by: Trond Myklebust

SUNRPC: introduce xdr_init_decode_pages

2011-05-29T17:52:32+00:00

Initialize xdr_stream and xdr_buf using an array of page pointers
and length of buffer.

Signed-off-by: Benny Halevy

Merge branch 'bugfixes' into nfs-for-2.6.38

2011-01-10T19:48:02+00:00

Conflicts:
	fs/nfs/nfs2xdr.c
	fs/nfs/nfs3xdr.c
	fs/nfs/nfs4xdr.c

NFS: Don't use vm_map_ram() in readdir

2011-01-10T19:45:01+00:00

vm_map_ram() is not available on NOMMU platforms, and causes trouble
on incoherrent architectures such as ARM when we access the page data
through both the direct and the virtual mapping.

The alternative is to use the direct mapping to access page data
for the case when we are not crossing a page boundary, but to copy
the data into a linear scratch buffer when we are accessing data
that spans page boundaries.

Signed-off-by: Trond Myklebust 
Tested-by: Marc Kleine-Budde 
Cc: stable@kernel.org  [2.6.37]