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 On 12/13/2013 12:01 PM, Benny Halevy wrote: > 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_lockowner on first match > > looks like a potential list corruption risk. > > [PATCH 2/2] nfsd4: ignore nfsv4.1 lockowners in nfsd4_release_lockowner > > I'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 majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
