doc/rbd/rbd-exclusive-locks: mention incompatibility with advisory locks

This is due to both using the same name for the lock at the RADOS level
("rbd_lock").

Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
(cherry picked from commit 2e83b77c9f610f42765266ff4d4d7bc2a635eac8)

diff --git a/doc/rbd/rbd-exclusive-locks.rst b/doc/rbd/rbd-exclusive-locks.rst
index f9b99dfb44305c7235f4595a13cdb1e2bbf61ec8..30be01fdb948e9f4932446709875eb7f6bcec32e 100644 (file)
--- a/doc/rbd/rbd-exclusive-locks.rst
+++ b/doc/rbd/rbd-exclusive-locks.rst
@@ -60,6 +60,10 @@ Exclusive locking is mostly transparent to the user:
    exclusive lock. This is exposed by the ``--exclusive`` option for ``rbd
    device map`` command.
 
+.. note::
+   The ``exclusive-lock`` feature is incompatible with RBD advisory locks
+   (the ``rbd lock add`` and ``rbd lock rm`` commands).
+
 
 Blocklisting
 ============