From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-lf0-x242.google.com (mail-lf0-x242.google.com
 [IPv6:2a00:1450:4010:c07::242])
 (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 21:24:18 +0200 (CEST)
Received: by mail-lf0-x242.google.com with SMTP id o124so8317292lfb.2
 for <dm-crypt@saout.de>; Thu, 07 Apr 2016 12:24:18 -0700 (PDT)
References: <1460039182.31097.7.camel@trentalancia.net>
 <5706897A.1000509@gmail.com> <1460051377.2289.1.camel@trentalancia.net>
 <5706A1B9.5000706@gmail.com> <1460054876.32268.9.camel@trentalancia.net>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <5706B3DF.50509@gmail.com>
Date: Thu, 7 Apr 2016 21:24:15 +0200
MIME-Version: 1.0
In-Reply-To: <1460054876.32268.9.camel@trentalancia.net>
Content-Type: text/plain; charset=utf-8
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 08:47 PM, Guido Trentalancia wrote:
> Hello.
> 
> My first message contains the debug information (last part of the
> strace output).

No, it does not. Please post debug information and NOT strace as
I described in the first reply...

Just add --debug to cryptsetup command and you have it (without strace).
It contains a lot of info that is needed to debug almost all kind of cryptsetup problem.

You also missed request to post distro version here.
Do you compile cryptsetup yourself?

Anyway, I am almost sure you are missing the udev dmsetup udevcomplete
call in udev, this is very common error.

> If you need other information, please let me know. Obviously I cannot
> post gdb output as the program does not crash, it simply gets stuck.

Strace or gdb info is not needed if not requested, --debug log is usually
enough to see what is going on.

And did you try that "dmsetup udevcomplete_all" I already suggested?
(once it is "stuck", run from another terminal - is should finish that command)

> The two versions show a different behaviour (the working version reads
> SELinux configuration, the broken version opens /dev/urandom and gets
> stuck), so the code must have changed.

I do not know about any change there.
Running code depends on compilation parameters, some basic info how code
behaves is in the debug log I am still waiting for...


Milan