diff options
| author | Susant Palai <spalai@redhat.com> | 2019-01-18 17:26:36 +0530 |
|---|---|---|
| committer | Amar Tumballi <amarts@redhat.com> | 2019-01-22 05:23:44 +0000 |
| commit | 3c556353cd1dde0593096c9e9e11b877403971f0 (patch) | |
| tree | 55e87230b06cf8ed635eef434dbb70a63dd736f2 /tests/basic/fencing/fencing-crash-conistency.t | |
| parent | 4f58d35f064e5fba3a02b7be8b2525ebe2114254 (diff) | |
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>
Diffstat (limited to 'tests/basic/fencing/fencing-crash-conistency.t')
| -rw-r--r-- | tests/basic/fencing/fencing-crash-conistency.t | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/basic/fencing/fencing-crash-conistency.t b/tests/basic/fencing/fencing-crash-conistency.t index cca8ee7343f..0c69411e90c 100644 --- a/tests/basic/fencing/fencing-crash-conistency.t +++ b/tests/basic/fencing/fencing-crash-conistency.t @@ -26,6 +26,7 @@ TEST "truncate -s 0 $M0/file" #enable mandatory locking TEST $CLI volume set $V0 locks.mandatory-locking forced +TEST $CLI volume set $V0 enforce-mandatory-lock on #write should pass TEST "echo "test" >> $M0/file" |