nfsd: handle seqid wraparound in nfsd4_preprocess_layout_stateid
Move the existing static function to an inline helper, and call it. Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Jeff Layton <jeff.layton@primarydata.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
This commit is contained in:
committed by
J. Bruce Fields
parent
64c59a3726
commit
14b7f4a1ed
@@ -4651,12 +4651,6 @@ grace_disallows_io(struct net *net, struct inode *inode)
|
||||
return opens_in_grace(net) && mandatory_lock(inode);
|
||||
}
|
||||
|
||||
/* Returns true iff a is later than b: */
|
||||
static bool stateid_generation_after(stateid_t *a, stateid_t *b)
|
||||
{
|
||||
return (s32)(a->si_generation - b->si_generation) > 0;
|
||||
}
|
||||
|
||||
static __be32 check_stateid_generation(stateid_t *in, stateid_t *ref, bool has_session)
|
||||
{
|
||||
/*
|
||||
@@ -4670,7 +4664,7 @@ static __be32 check_stateid_generation(stateid_t *in, stateid_t *ref, bool has_s
|
||||
return nfs_ok;
|
||||
|
||||
/* If the client sends us a stateid from the future, it's buggy: */
|
||||
if (stateid_generation_after(in, ref))
|
||||
if (nfsd4_stateid_generation_after(in, ref))
|
||||
return nfserr_bad_stateid;
|
||||
/*
|
||||
* However, we could see a stateid from the past, even from a
|
||||
|
||||
Reference in New Issue
Block a user