From: Arno Wagner <arno@wagner.name>
To: Jeremiah Moree <jtmoree@gmail.com>
Cc: dmcrypt <dm-crypt@saout.de>
Subject: [dm-crypt] Re: --disable-locks
Date: Fri, 24 Sep 2021 11:11:15 +0200 [thread overview]
Message-ID: <20210924091115.GB1446@tansi.org> (raw)
In-Reply-To: <CAAz2dUiPZmdJ2at2MYOfpjL=Lkabp3eBUBtDB_KFNfpD9KCrRQ@mail.gmail.com>
Well, I would say that header corruption is covered under
"concurrent user access problems", as the header is under
user control here.
But I see that items 1.9/1.10/1.11 are really in the wrong
section. They belong under "Setup" and "Common Problems".
I can move them and clarify the locking question.
Also 1.9/1.10 should really be one item.
Regards,
Arno
On Thu, Sep 23, 2021 at 15:01:29 CEST, Jeremiah Moree wrote:
> 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@saout.de
> To unsubscribe send an email to dm-crypt-leave@saout.de
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
next prev parent reply other threads:[~2021-09-24 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 13:01 [dm-crypt] --disable-locks Jeremiah Moree
2021-09-24 9:11 ` Arno Wagner [this message]
2021-09-24 17:33 ` [dm-crypt] --disable-locks Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210924091115.GB1446@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
--cc=jtmoree@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox