From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: James Lee <jlee-RWYTM8lfiZY4k1Tz1RznXQC/G2K4zDHf@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] crypt: Wait for udev to settle before unlocking disk
Date: Wed, 31 Jul 2013 15:51:05 +0200 [thread overview]
Message-ID: <51F91649.3090203@redhat.com> (raw)
In-Reply-To: <1375128622-8307-1-git-send-email-jlee-RWYTM8lfiZY4k1Tz1RznXQC/G2K4zDHf@public.gmane.org>
On 07/29/2013 10:10 PM, James Lee wrote:
> To eliminate a race condition that occurs when unlocking one device
> depends on the result of unlocking a device before it, the crypt
> module must wait for udev to settle between each unlock attempt.
>
> Example
>
> /etc/crypttab:
>
> keyfile /dev/md1 none luks
> sda4_crypt /dev/sda4 /dev/mapper/keyfile luks
> sdb4_crypt /dev/sdb4 /dev/mapper/keyfile luks
>
> Without this patch, sometimes /dev/sda4 fails to unlock because udev
> doesn't have time to create /dev/mapper/keyfile before it's needed.
> ---
> modules.d/90crypt/parse-crypt.sh | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/modules.d/90crypt/parse-crypt.sh b/modules.d/90crypt/parse-crypt.sh
> index 961ec61..4e42d59 100755
> --- a/modules.d/90crypt/parse-crypt.sh
> +++ b/modules.d/90crypt/parse-crypt.sh
> @@ -23,7 +23,7 @@ else
> {
> printf -- 'ENV{ID_FS_TYPE}=="crypto_LUKS", '
> printf -- 'ENV{ID_FS_UUID}=="*%s*", ' $luksid
> - printf -- 'RUN+="%s --unique --onetime ' $(command -v initqueue)
> + printf -- 'RUN+="%s --settled --unique --onetime ' $(command -v initqueue)
> printf -- '--name cryptroot-ask-%%k %s ' $(command -v cryptroot-ask)
> printf -- '$env{DEVNAME} luks-$env{ID_FS_UUID} %s"\n' $tout
> } >> /etc/udev/rules.d/70-luks.rules.new
> @@ -31,7 +31,7 @@ else
> {
> printf -- 'ENV{ID_FS_TYPE}=="crypto_LUKS", '
> printf -- 'ENV{ID_FS_UUID}=="*%s*", ' $luksid
> - printf -- 'RUN+="%s --unique --onetime ' $(command -v initqueue)
> + printf -- 'RUN+="%s --settled --unique --onetime ' $(command -v initqueue)
> printf -- '--name systemd-cryptsetup-%%k %s start ' $(command -v systemctl)
> printf -- 'systemd-cryptsetup@luks$$(dev_unit_name -$env{ID_FS_UUID}).service"\n'
> } >> /etc/udev/rules.d/70-luks.rules.new
> @@ -51,13 +51,13 @@ else
> if [ -z "$DRACUT_SYSTEMD" ]; then
> {
> printf -- 'ENV{ID_FS_TYPE}=="crypto_LUKS", RUN+="%s ' $(command -v initqueue)
> - printf -- '--unique --onetime --name cryptroot-ask-%%k '
> + printf -- '--unique --settled --onetime --name cryptroot-ask-%%k '
> printf -- '%s $env{DEVNAME} luks-$env{ID_FS_UUID} %s"\n' $(command -v cryptroot-ask) $tout
> } >> /etc/udev/rules.d/70-luks.rules.new
> else
> {
> printf -- 'ENV{ID_FS_TYPE}=="crypto_LUKS", RUN+="%s ' $(command -v initqueue)
> - printf -- '--unique --onetime --name crypt-run-generator-%%k '
> + printf -- '--unique --settled --onetime --name crypt-run-generator-%%k '
> printf -- '%s $env{DEVNAME} luks-$env{ID_FS_UUID}"\n' $(command -v crypt-run-generator)
> } >> /etc/udev/rules.d/70-luks.rules.new
> fi
>
thanks! pushed
prev parent reply other threads:[~2013-07-31 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 20:10 [PATCH] crypt: Wait for udev to settle before unlocking disk James Lee
[not found] ` <1375128622-8307-1-git-send-email-jlee-RWYTM8lfiZY4k1Tz1RznXQC/G2K4zDHf@public.gmane.org>
2013-07-31 13:51 ` Harald Hoyer [this message]
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=51F91649.3090203@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jlee-RWYTM8lfiZY4k1Tz1RznXQC/G2K4zDHf@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.