All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Ali Reza Sajedi <arsajedi@khanehjou.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Long Unlocking Time
Date: Thu, 25 Mar 2010 17:22:36 +0100	[thread overview]
Message-ID: <4BAB8DCC.6090507@redhat.com> (raw)
In-Reply-To: <6559AA6A9E5C43D6A3494FB045B91615@AliPC>

On 03/25/2010 04:56 PM, Ali Reza Sajedi wrote:
> For this purpose I have a perl script called via a dev-rule when the drive 
> is attached.

If it is cryptsetup 1.0.6 it internally calls udevadm settle, you
are running from udev rule, so it waits for itself ->deadlock -> timeout.

I later version is this removed, BUT:
If you are using device-mapper with udev enabled, its need to synchronise
device node creation, which happens from the last dm udev-rule, but you are blocked
in rule before -> deadlock -> timeout (maybe).

Best do not do these operations from udev rule at all.

Maybe if it fork itself, it can work somehow. Anyway it is probably better
to not add such commands directly to udev rule, but in some other system
which registers for udev events (using some d-bus message or whatever).

Someone probably can suggest better desktop solution...

Milan

  parent reply	other threads:[~2010-03-25 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 15:56 [dm-crypt] Long Unlocking Time Ali Reza Sajedi
2010-03-25 16:10 ` Bryan Kadzban
2010-03-25 16:22 ` Milan Broz [this message]
2010-03-25 17:10   ` Thomas Bächler
2010-03-25 17:28     ` Milan Broz
2010-03-25 20:25       ` Ali Reza Sajedi
2010-03-25 21:45       ` Ali Reza Sajedi
2010-03-27 11:09         ` [dm-crypt] Change Language Ali Reza Sajedi
2010-03-27 11:45           ` Sven Eschenberg
2010-03-29 20:47             ` Ali Reza Sajedi
2010-03-25 17:56   ` [dm-crypt] Long Unlocking Time Sven Eschenberg

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=4BAB8DCC.6090507@redhat.com \
    --to=mbroz@redhat.com \
    --cc=arsajedi@khanehjou.com \
    --cc=dm-crypt@saout.de \
    /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.