J. Bruce Fields 90d700b779 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>
2012-05-31 20:30:07 -04:00
..
2012-03-28 09:58:38 -07:00
2012-04-03 20:46:09 -05:00
2012-03-31 16:03:16 -04:00
2012-03-21 10:15:51 -07:00
2012-03-28 15:58:21 -07:00
2012-03-30 17:31:56 -07:00
2012-03-20 21:29:52 -04:00
2012-03-20 21:29:38 -04:00
2012-03-30 17:31:56 -07:00
2012-03-23 09:27:40 -07:00
2012-03-28 15:58:21 -07:00
2012-03-20 21:29:46 -04:00
2012-03-20 21:29:46 -04:00
2012-01-03 22:52:39 -05:00
2012-03-28 10:07:27 -07:00
2012-03-20 21:29:51 -04:00
2012-04-05 15:25:50 -07:00
2012-03-20 21:29:38 -04:00