nfsd4: simpler ordering of setclientid_confirm checks
authorJ. Bruce Fields <bfields@redhat.com>
Sat, 19 May 2012 17:55:22 +0000 (13:55 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Fri, 1 Jun 2012 00:30:07 +0000 (20:30 -0400)
commit90d700b7792a1a7d57554620796df46246e26ce6
treeaaea6476800b50552166505938932cd9dc98e93c
parentf3d03b9202e4303f0e687f93ffeab87724f6dcfb
nfsd4: simpler ordering of setclientid_confirm checks

The cases here divide into two main categories:

- if there's an uncomfirmed record with a matching verifier,
  then this is a "normal", succesful case: we're either creating
  a new client, or updating an existing one.
- otherwise, this is a weird case: a replay, or a server reboot.

Reordering to reflect that makes the code a bit more concise and the
logic a lot easier to understand.

Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c