1
0
mirror of https://github.com/gluster/glusterfs.git synced 2026-02-07 12:48:38 +01:00
Files
glusterfs/tests/basic/fencing/fence-basic.t
Susant Palai 09e7eca47d 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 <spalai@redhat.com>
2019-01-18 17:26:36 +05:30

31 lines
729 B
Bash
Executable File

#!/bin/bash
. $(dirname $0)/../../include.rc
. $(dirname $0)/../../volume.rc
cleanup;
TEST glusterd
TEST pidof glusterd
TEST $CLI volume info;
TEST $CLI volume create $V0 $H0:$B0/brick1
EXPECT 'Created' volinfo_field $V0 'Status';
TEST $CLI volume start $V0;
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`
TEST build_tester $(dirname $0)/fence-basic.c -lgfapi -ggdb
TEST $(dirname $0)/fence-basic $H0 $V0 $logdir
cleanup_tester $(dirname $0)/fence-basic
cleanup;