mirror of
https://github.com/torvalds/linux.git
synced 2026-05-27 00:22:00 +02:00
nfsd: remove obsolete comment from nfs4_alloc_stid
idr_alloc_cyclic() is what guarantees that now, not this long-gone trick. Signed-off-by: Jeff Layton <jlayton@kernel.org> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
This commit is contained in:
parent
d917d78311
commit
387625808c
|
|
@ -946,15 +946,6 @@ struct nfs4_stid *nfs4_alloc_stid(struct nfs4_client *cl, struct kmem_cache *sla
|
|||
spin_lock_init(&stid->sc_lock);
|
||||
INIT_LIST_HEAD(&stid->sc_cp_list);
|
||||
|
||||
/*
|
||||
* It shouldn't be a problem to reuse an opaque stateid value.
|
||||
* I don't think it is for 4.1. But with 4.0 I worry that, for
|
||||
* example, a stray write retransmission could be accepted by
|
||||
* the server when it should have been rejected. Therefore,
|
||||
* adopt a trick from the sctp code to attempt to maximize the
|
||||
* amount of time until an id is reused, by ensuring they always
|
||||
* "increase" (mod INT_MAX):
|
||||
*/
|
||||
return stid;
|
||||
out_free:
|
||||
kmem_cache_free(slab, stid);
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user