a couple fixes in nfsd4_release_lockowner
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] a couple fixes in nfsd4_release_lockowner
changes from v1:
[PATCH v2 1/2] nfsd4: break from inner lookup loop in nfsd4_release_lockowner on first match
- initialize lo_list
- in case locks our found delete all previous matches from temporary list
[PATCH 2/2] nfsd4: ignore nfsv4.1 lockowners in nfsd4_release_lockowner
- added comment
Quoted 19 lines · Benny Halevy
Bruce, while working on the state mutex elimination stuff I saw these two issues in
nfsd4_release_lockowner. These patches are untested but I just wanted to quickly get your take on them.[PATCH 1/2] nfsd4: break from inner lookup loop in
nfsd4_release_lockowneron first matchlooks like a potential list corruption risk.
[PATCH 2/2] nfsd4: ignore nfsv4.1 lockowners in
nfsd4_release_lockownerI'm not sure that 100% needed but since we keep both nfsv4.0 and v4.1 owners hashed on the same lists we don't want a v4.0 operation to accidentally touch v4.1 state.
Benny
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html