While searching through the source code I came upon docs/LUKS-locking.txt.
From previous discussions on this list I understood the locking to be only for protection against concurrent user access. This is how I wrote the FAQ entry that is now in the docs.
From this new-to-me doc it seems that locking is to also prevent header corruption. I am surprised no one pointed this out in discussions so there is a chance I may be misunderstanding.
Specifically, this was in a discussion about --disable-locks. Am I correct in stating:
Using --disable-locks I risk
* concurrent user access problems
* header corruption
--
JT
_______________________________________________ dm-crypt mailing list -- dm-crypt@xxxxxxxx To unsubscribe send an email to dm-crypt-leave@xxxxxxxx
