Trond Myklebust 8e35f8e7c6 NLM: Fix a regression in lockd ... Nick Bowler reports: There are no unusual messages on the client... but I just logged into the server and I see lots of messages of the following form: nfsd: request from insecure port (192.168.8.199:35766)! nfsd: request from insecure port (192.168.8.199:35766)! nfsd: request from insecure port (192.168.8.199:35766)! nfsd: request from insecure port (192.168.8.199:35766)! nfsd: request from insecure port (192.168.8.199:35766)! Bisected to commit 9247685088 (SUNRPC: Properly initialize sock_xprt.srcaddr in all cases) Apparently, removing the 'transport->srcaddr.ss_family = family' from xs_create_sock() triggers this due to nlmclnt_lookup_host() incorrectly initialising the srcaddr family to AF_UNSPEC. Reported-by: Nick Bowler <nbowler@elliptictech.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>		2010-11-15 20:44:26 -05:00
..
clntlock.c	lockd: Remove BKL from the client	2010-09-22 09:50:35 -04:00
clntproc.c	lockd: Remove BKL from the client	2010-09-22 09:50:35 -04:00
grace.c	nfsd: common grace period control	2008-10-03 16:19:02 -04:00
host.c	NLM: Fix a regression in lockd	2010-11-15 20:44:26 -05:00
Makefile	nfsd: common grace period control	2008-10-03 16:19:02 -04:00
mon.c	sunrpc: Add net to rpc_create_args	2010-10-01 17:18:56 -04:00
svc.c	lockd: push lock_flocks down	2010-10-27 21:39:39 +02:00
svc4proc.c	lockd: Mostly remove BKL from the server	2010-09-22 15:32:58 -04:00
svclock.c	lockd: fix nlmsvc_notify_blocked locking	2010-10-27 21:39:50 +02:00
svcproc.c	lockd: Mostly remove BKL from the server	2010-09-22 15:32:58 -04:00
svcshare.c	lockd: fix sparse warning in svcshare.c	2008-04-23 16:13:39 -04:00
svcsubs.c	lockd: push lock_flocks down	2010-10-27 21:39:39 +02:00
xdr.c	headers: utsname.h redux	2009-09-23 18:13:10 -07:00
xdr4.c	headers: utsname.h redux	2009-09-23 18:13:10 -07:00