doc: specify RBD_LOCK_MODE_EXCLUSIVE for exclusive-lock

The exclusive-lock could be transited transparently between clients
after finishing write operation. To disable "transparent" transition,
it needs to acquire the lock with RBD_LOCK_MODE_EXCLUSIVE.

Signed-off-by: Changcheng Liu <changcheng.liu@aliyun.com>

diff --git a/doc/rbd/rbd-exclusive-locks.rst b/doc/rbd/rbd-exclusive-locks.rst
index f07651d32eda9cf1fb8dc8dd5df0f31323443216..cedc0d11191a790e9a1140ffd0a18083b20a32b5 100644 (file)
--- a/doc/rbd/rbd-exclusive-locks.rst
+++ b/doc/rbd/rbd-exclusive-locks.rst
@@ -36,7 +36,9 @@ Exclusive locking is mostly transparent to the user.
 Note that it is perfectly possible for two or more concurrently
 running processes to merely open the image, and also to read from
 it. The client acquires the exclusive lock only when attempting to
-write to the image.
+write to the image. To disable transparent lock transitions between
+multiple clients, it needs to acquire the lock specifically with
+``RBD_LOCK_MODE_EXCLUSIVE``.
 
 
 Blacklisting