Commit c1c54164 authored by Milan Broz's avatar Milan Broz

Add a note about locking to man page.

parent b4782809
......@@ -1339,6 +1339,16 @@ cryptsetup FAQ for an example.
When device mapping is active, you can see the loop backing file in
the status command output. Also see losetup(8).
.SH LUKS2 header locking
The LUKS2 on-disk metadata is updated in several steps and
to achieve proper atomic update, there is a locking mechanism.
For an image in file, code uses \fIflock(2)\fR system call.
For a block device, lock is perfomed over a special file stored
in a locking directory (by default \fI/run/lock/cryptsetup\fR).
The locking directory should be created with the proper security
context by the distribution during the boot-up phase.
Only LUKS2 uses locks, other formats do not use this mechanism.
The \fIreload\fR action is no longer supported.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment