All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: "<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>"
	<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Please revert commit fa0115c3c06176bd0fdfcd8966021979ec84f3d7
Date: Wed, 24 Jun 2009 08:59:38 +0200	[thread overview]
Message-ID: <4A41CEDA.9020504@bfh.ch> (raw)
In-Reply-To: <4A408358.7050706-omB+W0Dpw2o@public.gmane.org>

Seewer Philippe wrote:
> Commit fa0115c3c06176bd0fdfcd8966021979ec84f3d7 moved calling
> cryptsetup from the mount hook to inside a udev rule. While this is a 
> good idea it causes more problems than it solves:
> 
> cryptsetup version 1.6 (and possibly earlier versions) calls
> 'udevadm settle' on it's own. This must not be done from inside
> udev rules as it potentially results in a deadlock depending
> on udev version.

A short amendment to this:

- Fedora cryptsetup is patched, removing the udevadm settle altogether.
That's why it was working for most of you. (Thanks to Warren for helping
to debug this)

- In addition I don't think its a good idea to include anything in a
udev-rule that does user interaction, since udev has an built-in
event-timeout.

> 
> Thank you,
> Philippe
> -- 
> To unsubscribe from this list: send the line "unsubscribe initramfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-06-24  6:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  7:25 Please revert commit fa0115c3c06176bd0fdfcd8966021979ec84f3d7 Seewer Philippe
     [not found] ` <4A408358.7050706-omB+W0Dpw2o@public.gmane.org>
2009-06-24  6:59   ` Seewer Philippe [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=4A41CEDA.9020504@bfh.ch \
    --to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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.