[Cluster-devel] GFS2: Pull request #2 (merge window)

Hi Linus, Please consider pulling the following additional 3 patches for the GFS2 file system. Regards, Bob Peterson The following changes since commit e241e3f2bf975788a1b70dff2eb5180ca395b28e: Merge tag 'for_linus' of

[Cluster-devel] [PATCH 2/3] gfs2: Stop using rhashtable_walk_peek

From: Andreas Gruenbacher Function rhashtable_walk_peek is problematic because there is no guarantee that the glock previously returned still exists; when that key is deleted, rhashtable_walk_peek can end up returning a different key, which will cause an inconsistent glock

[Cluster-devel] [PATCH 0/3] GFS2: Second pre-pull patch posting (merge window)

Hi, We decided to request the latest three patches to be merged into this merge window while it's still open. 1. The first patch adds a new function to lockref: lockref_put_not_zero 2. The second patch fixes GFS2's glock dump code so it uses the new lockref function. This fixes a problem

[Cluster-devel] [PATCH 1/3] lockref: Add lockref_put_not_zero

From: Andreas Gruenbacher Put a lockref unless the lockref is dead or its count would become zero. This is the same as lockref_put_or_lock except that the lock is never left held. Signed-off-by: Andreas Gruenbacher Signed-off-by: Bob Peterson

[Cluster-devel] [PATCH 3/3] GFS2: Minor improvements to comments and documentation

This patch simply fixes some comments and the gfs2-glocks.txt file: Places where i_rwsem was called i_mutex, and adding i_rw_mutex. Signed-off-by: Bob Peterson --- Documentation/filesystems/gfs2-glocks.txt | 5 +++-- fs/gfs2/bmap.c| 2 +-

[Cluster-devel] [PATCH 2/3] gfs2: Stop using rhashtable_walk_peek

From: Andreas Gruenbacher Function rhashtable_walk_peek is problematic because there is no guarantee that the glock previously returned still exists; when that key is deleted, rhashtable_walk_peek can end up returning a different key, which will cause an inconsistent glock

[Cluster-devel] [PATCH 1/3] lockref: Add lockref_put_not_zero

From: Andreas Gruenbacher Put a lockref unless the lockref is dead or its count would become zero. This is the same as lockref_put_or_lock except that the lock is never left held. Signed-off-by: Andreas Gruenbacher Signed-off-by: Bob Peterson

Re: [Cluster-devel] [PATCH v2 0/2] gfs2: Stop using rhashtable_walk_peek

- Original Message - > Here's a second version of the patch (now a patch set) to eliminate > rhashtable_walk_peek in gfs2. > > The first patch introduces lockref_put_not_zero, the inverse of > lockref_get_not_zero. > > The second patch eliminates rhashtable_walk_peek in gfs2. In >