From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Thu, 25 Mar 2010 18:29:04 +0100 (CET)
Message-ID: <4BAB9D58.9050507@redhat.com>
Date: Thu, 25 Mar 2010 18:28:56 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <6559AA6A9E5C43D6A3494FB045B91615@AliPC>
	<4BAB8DCC.6090507@redhat.com> <4BAB98F0.403@archlinux.org>
In-Reply-To: <4BAB98F0.403@archlinux.org>
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [dm-crypt] Long Unlocking Time
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=subscribe>
To: =?ISO-8859-15?Q?Thomas_B=E4chler?= <thomas@archlinux.org>
Cc: dm-crypt@saout.de, Ali Reza Sajedi <arsajedi@khanehjou.com>

On 03/25/2010 06:10 PM, Thomas B=E4chler wrote:
> Am 25.03.2010 17:22, schrieb Milan Broz:
> In my opinion, udev is the right place for such tasks, unless you want
> to use or even write a daemon that listens for events using libudev -
> which is overkill for such an easy task.

Udev rules should maintain /dev, not run time expensive operation which
will block all following events for the device.

Anyway, all I want to say is:
with cryptsetup 1.0.6 it will deadlocks because of internal "udevadm settle=
",
and this is what you are probably seeing. You cat try update if you have th=
is version.

Milan