diff options
author | Krutika Dhananjay <kdhananj@redhat.com> | 2014-04-24 16:37:05 +0530 |
---|---|---|
committer | Niels de Vos <ndevos@redhat.com> | 2014-05-08 06:00:56 -0700 |
commit | d8014f53c22a7da2d7b38e7d3215aa83e3e51d0d (patch) | |
tree | a5230832fc109449a2f86577fadb57748a4e049c /tests | |
parent | 45a0322066513259e61c7a4b1b1ed1a0bd3a0827 (diff) |
features/locks: Remove stale entrylk objects from 'blocked_locks' list
Backport of http://review.gluster.org/7560
* In the event of a DISCONNECT from a client, as part of cleanup,
entrylk objects are not removed from the blocked_locks list before
being unref'd and freed, causing the brick process to crash at
some point when the (now) stale object is accessed again in the list.
* Also during cleanup, it is pointless to try and grant lock to a
previously blocked entrylk (say L1) as part of releasing another
conflicting lock (L2), (which is a side-effect of L1 not being
deleted from blocked_locks list before grant_blocked_entry_locks()
in cleanup) if L1 is also associated with the DISCONNECTing client.
This patch fixes the problem.
Change-Id: Ie077f8eeb61c5505f047a8fdaac67db32e5d4270
BUG: 1089470
Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
Reviewed-on: http://review.gluster.org/7576
Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions