From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com
 [IPv6:2a00:1450:400c:c09::243])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu,  7 Apr 2016 18:23:25 +0200 (CEST)
Received: by mail-wm0-x243.google.com with SMTP id a140so22692238wma.2
 for <dm-crypt@saout.de>; Thu, 07 Apr 2016 09:23:25 -0700 (PDT)
References: <1460039182.31097.7.camel@trentalancia.net>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <5706897A.1000509@gmail.com>
Date: Thu, 7 Apr 2016 18:23:22 +0200
MIME-Version: 1.0
In-Reply-To: <1460039182.31097.7.camel@trentalancia.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck
 after open/close
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: Guido Trentalancia <guido@trentalancia.net>, dm-crypt@saout.de

On 04/07/2016 04:26 PM, Guido Trentalancia wrote:
> Hello.
> 
> Cryptsetup version 1.7.0 and 1.7.1 gets stuck on luksOpen and luksClose
> immediately after the device has been opened or closed.

If it is stuck on semop operation, then it is problem of underlying
device-mapper library (that uses system semaphores for synchronization).

Usually it is caused by a misconfiguration of udev rules (there must be udev
rule calling dmsetup udevcomplete otherwise it ends like in your case).

Please check that you have these udev rules installed - they are
usually part of lvm2/dsmetup subpackage (depends on distro, for example in Debian
it is /lib/udev/rules.d/55-dm.rules).

...
> 
> The device is closed correctly, however the cryptsetup process has to
> be killed again to get the shell prompt back.

Does calling "dmsetup udevcomplete_all" help? If so, see above.

> Previous versions (such as 1.6.8 and earlier ones) are not affected by
> this bug.

I guess 1.6.8 is either compiled without udev support or you reinstalled something.
(cryptsetup 1.7.0 does not contain any related changes to this problem).

Please better post cryptsetup command with --debug, strace only on request
(it does not contain important information, moreove ot can contain your password).
Also always mention your distro and version.

Thanks,
Milan