nfsd: clean up comments over nfs4_client definition
nfsd fault injection has been deprecated since commit9d60d93198
("Deprecate nfsd fault injection") and removed by commite56dc9e294
("nfsd: remove fault injection code") So remove the outdated parts about fault injection. Signed-off-by: Chen Hanxiao <chenhx.fnst@fujitsu.com> Reviewed-by: Jeff Layton <jlayton@kernel.org> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
This commit is contained in:
parent
e084ee673c
commit
f81040276a
|
@ -334,8 +334,9 @@ enum {
|
|||
* 0. If they are not renewed within a lease period, they become eligible for
|
||||
* destruction by the laundromat.
|
||||
*
|
||||
* These objects can also be destroyed prematurely by the fault injection code,
|
||||
* or if the client sends certain forms of SETCLIENTID or EXCHANGE_ID updates.
|
||||
* These objects can also be destroyed if the client sends certain forms of
|
||||
* SETCLIENTID or EXCHANGE_ID operations.
|
||||
*
|
||||
* Care is taken *not* to do this however when the objects have an elevated
|
||||
* refcount.
|
||||
*
|
||||
|
@ -343,7 +344,7 @@ enum {
|
|||
*
|
||||
* o Each nfs4_clients is also hashed by name (the opaque quantity initially
|
||||
* sent by the client to identify itself).
|
||||
*
|
||||
*
|
||||
* o cl_perclient list is used to ensure no dangling stateowner references
|
||||
* when we expire the nfs4_client
|
||||
*/
|
||||
|
|
Loading…
Reference in New Issue