From 3c556353cd1dde0593096c9e9e11b877403971f0 Mon Sep 17 00:00:00 2001 From: Susant Palai Date: Fri, 18 Jan 2019 17:26:36 +0530 Subject: locks/fencing: Add a security knob for fencing There is a low level security issue with fencing since one client can preempt another client's lock. This patch does not completely eliminate the issue of a client misbehaving, but certainly it adds a security layer for default use cases that does not need fencing. Change-Id: I55cd15f2ed1ae0f2556e3d27a2ef4bc10fdada1c updates: #466 Signed-off-by: Susant Palai --- tests/basic/fencing/fence-basic.t | 2 ++ 1 file changed, 2 insertions(+) (limited to 'tests/basic/fencing/fence-basic.t') diff --git a/tests/basic/fencing/fence-basic.t b/tests/basic/fencing/fence-basic.t index 080507c2ba5..30f379e7b20 100755 --- a/tests/basic/fencing/fence-basic.t +++ b/tests/basic/fencing/fence-basic.t @@ -18,6 +18,8 @@ EXPECT 'Started' volinfo_field $V0 'Status'; TEST $CLI volume set $V0 diagnostics.client-log-flush-timeout 30 TEST $CLI volume set $V0 performance.write-behind off TEST $CLI volume set $V0 locks.mandatory-locking forced +TEST $CLI volume set $V0 enforce-mandatory-lock on + logdir=`gluster --print-logdir` -- cgit