linux-toradex.git/fs/lockd/xdr4.c, branch v2.6.28.4

lockd: Remove unused fields in the nlm_reboot structure

2008-10-03T21:02:35+00:00

The nlm_reboot structure is used to store information provided by the
NSM_NOTIFY procedure.  This procedure is not specified by the NLM or NSM
protocols, other than to say that the procedure can be used to transmit
information private to a particular NLM/NSM implementation.

For Linux, the callback arguments include the name of the monitored host,
the new NSM state of the host, and a 16-byte private opaque.

As a clean up, remove the unused fields and the server-side XDR logic that
decodes them.

Signed-off-by: Chuck Lever 
Signed-off-by: J. Bruce Fields

LOCKD: Convert printk's to dprintk's in lockd XDR routines

2007-10-09T21:17:12+00:00

Due to recent edict to remove or replace printk's that might flood the
system log.

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

NLM: Fix sparse warnings

2007-05-14T23:33:46+00:00

 - fs/lockd/xdr4.c:140:27: warning: incorrect type in argument 2 (different
   explicit signedness)
 - fs/lockd/xdr4.c:141:27: warning: incorrect type in argument 2 (different
   explicit signedness)
 - fs/lockd/xdr4.c:432:28: warning: incorrect type in argument 2 (different
   explicit signedness)
 - fs/lockd/xdr4.c:433:28: warning: incorrect type in argument 2 (different
   explicit signedness)
 - fs/lockd/xdr4.c:587:20: warning: symbol 'nlm_version4' was not declared.
   Should it be static?

Signed-off-by: Trond Myklebust

SUNRPC: RPC buffer size estimates are too large

2007-05-01T05:17:10+00:00

The RPC buffer size estimation logic in net/sunrpc/clnt.c always
significantly overestimates the requirements for the buffer size.
A little instrumentation demonstrated that in fact rpc_malloc was never
allocating the buffer from the mempool, but almost always called kmalloc.

To compute the size of the RPC buffer more precisely, split p_bufsiz into
two fields; one for the argument size, and one for the result size.

Then, compute the sum of the exact call and reply header sizes, and split
the RPC buffer precisely between the two.  That should keep almost all RPC
buffers within the 2KiB buffer mempool limit.

And, we can finally be rid of RPC_SLACK_SPACE!

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

NLM: Shrink the maximum request size of NLM4 requests

2007-05-01T05:17:09+00:00

NLM version 4 requests estimate the call and reply header sizes rather
conservatively, using the very maximum size allowed in the protocol even
though Linux always uses only a small fraction of the allowable space.

Reduce the size of caller and lock arguments to conserve RPC buffer space
while XDR encoding NLM4 arguments.  Add compile-time checks to ensure the
hostname string won't overflow NLM protocol maximums.

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

[PATCH] lockd endianness annotations

2006-12-13T17:05:52+00:00

Annotated, all places switched to keeping status net-endian.

Signed-off-by: Al Viro 
Acked-by: Trond Myklebust 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] lockd endianness annotations

2006-10-20T17:26:40+00:00

Signed-off-by: Alexey Dobriyan 
Signed-off-by: Al Viro 
Acked-by: Trond Myklebust 
Acked-by: Neil Brown 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

SUNRPC: display human-readable procedure name in rpc_iostats output

2006-03-20T18:44:22+00:00

Add fields to the rpc_procinfo struct that allow the display of a
human-readable name for each procedure in the rpc_iostats output.

Also fix it so that the NFSv4 stats are broken up correctly by
sub-procedure number.  NFSv4 uses only two real RPC procedures:
NULL, and COMPOUND.

Test plan:
Mount with NFSv2, NFSv3, and NFSv4, and do "cat /proc/self/mountstats".

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

lockd: Don't expose the process pid to the NLM server

2006-03-20T18:44:06+00:00

Instead we use the nlm_lockowner->pid.

Signed-off-by: Trond Myklebust

NLM: fix parsing of sm notify procedure

2006-01-06T19:58:54+00:00

 The procedure that decodes statd sm_notify call seems to be skipping a
 few arguments.  How did this ever work?

 >From folks at Polyserve.

 Signed-off-by: J. Bruce Fields 
 Signed-off-by: Trond Myklebust