NFSv4: handle lack of clientaddr in option string
commit0a87cf128f3d3bc6aa7b1040e73109c974ed875a
authorJeff Layton <jlayton@redhat.com>
Wed, 18 Jul 2007 15:28:43 +0000 (18 11:28 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Thu, 19 Jul 2007 19:21:40 +0000 (19 15:21 -0400)
tree07bfeee89a7df2377cdb2b7d6770d66edd8bb308
parentf9d888fcd9665b863fa042212a3ee7b4c51399f6
NFSv4: handle lack of clientaddr in option string

If a NFSv4 mount is attempted  with string based options, and the
option string doesn't contain a clientaddr= option, the kernel will
currently oops. Check for this situation and return a proper error.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/super.c