From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id kr3xqOH7WFxQ for <dm-crypt@saout.de>;
 Tue, 19 Feb 2013 12:37:09 +0100 (CET)
Received: from mail-ea0-f177.google.com (mail-ea0-f177.google.com
 [209.85.215.177])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Tue, 19 Feb 2013 12:37:09 +0100 (CET)
Received: by mail-ea0-f177.google.com with SMTP id n13so2799702eaa.36
 for <dm-crypt@saout.de>; Tue, 19 Feb 2013 03:37:08 -0800 (PST)
Message-ID: <512363E1.7040703@gmail.com>
Date: Tue, 19 Feb 2013 12:37:05 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <CAFnMBaRGXe952cN-n=s3v9CYgW8nPidisin+CJhEixEOP0o9AQ@mail.gmail.com>
In-Reply-To: <CAFnMBaRGXe952cN-n=s3v9CYgW8nPidisin+CJhEixEOP0o9AQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] inconsistent behavior btw a binary and library call
 when closing truecrypt volume made up of multiple algorithms
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: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de

On 02/18/2013 05:58 AM, .. ink .. wrote:
> 
> test:
> 
> 1. create a truecrypt volume using multiple algorithms,i went with AES-twofist-serpent
> 2. open the volume using cryptsetup with "cryptsetup tcryptOpen ttt ttt"
> 3. ls -l /dev/mapper/ will give:
> 
> crw------- 1 root root 10, 236 Feb 17 22:37 /dev/mapper/control
> lrwxrwxrwx 1 root root       7 Feb 17 23:45 /dev/mapper/ttt -> ../dm-2
> lrwxrwxrwx 1 root root       7 Feb 17 23:45 /dev/mapper/ttt_1 -> ../dm-1
> lrwxrwxrwx 1 root root       7 Feb 17 23:45 /dev/mapper/ttt_2 -> ../dm-0
> 
> It looks like 3 mapper will be created,each per algorithm.
> 
> closing the mapper with " cryptsetup tcryptClose ttt" will remove all three mappers expected.
> 
> closing the mapper through the library "crypt_deactivate( NULL,"ttt"
> )" will not remove all 3,just the "ttt" one.With the library call,
> all 3 seem to require to be removed individually.> 
> Is this behavior of the library expected?

Kind of... if NULL is in context. If you use context (init_by_name) it should work.

Anyway, I filled (and added some comment)
http://code.google.com/p/cryptsetup/issues/detail?id=147
(also for other problems you reported - see issues 146,148)
will update it there once I have time to fix it.

Thanks,
Milan