From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tazok.id0@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 Gut1-b6KDoBI for <dm-crypt@saout.de>;
 Fri,  1 Jun 2012 12:52:29 +0200 (CEST)
Received: from mail-ey0-f178.google.com (mail-ey0-f178.google.com
 [209.85.215.178])
 (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>; Fri,  1 Jun 2012 12:52:29 +0200 (CEST)
Received: by eaae11 with SMTP id e11so527298eaa.37
 for <dm-crypt@saout.de>; Fri, 01 Jun 2012 03:52:29 -0700 (PDT)
Message-ID: <4FC89EF4.8080408@gmail.com>
Date: Fri, 01 Jun 2012 12:52:36 +0200
From: =?ISO-8859-1?Q?Javier_Juan_Mart=EDnez_Cabez=F3n?= <tazok.id0@gmail.com>
MIME-Version: 1.0
References: <CAFnMBaTKyAy3=O5LBwFWr-chY_+Zu-tVUX7+vDAWnDah=kuc5g@mail.gmail.com>
In-Reply-To: <CAFnMBaTKyAy3=O5LBwFWr-chY_+Zu-tVUX7+vDAWnDah=kuc5g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] inconsistency in opening multiple mappers on the
 same device
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: dm-crypt@saout.de

On 01/06/12 00:12, .. ink .. wrote:
> I read the announcement of 1.4.3 and decided to do a simple test on
> opening multiple mappers on the same device and this is what i found
> out:
> 
> test using cryptsetup 1.4.3
> 
> [root@mtz ink]# echo -n xxx | cryptsetup create zzz xxx
> [root@mtz ink]# echo -n xxx | cryptsetup create zzz xxx
> Device zzz already exists.
> [root@mtz ink]# echo -n xxx | cryptsetup create yyy xxx
> 
> [root@mtz ink]# ls -l /dev/mapper/
> total 0
> crw------- 1 root root 10, 236 May 29 14:46 control
> lrwxrwxrwx 1 root root       7 May 31 18:01 yyy -> ../dm-1
> lrwxrwxrwx 1 root root       7 May 31 18:01 zzz -> ../dm-0
> 
> [root@mtz ink]# zuluCrypt-cli -P -d /dev/mapper/zzz
> /home/ink/xxx
> [root@mtz ink]# zuluCrypt-cli -P -d /dev/mapper/yyy
> /home/ink/xxx
> [root@mtz ink]#
> 
> It looks like by default, cryptsetup does not allow opening more than
> one mapper on the same device bu it only checks the mapper name, not
> the device behind the mapper and hence it allows opening of multiple
> mappers on the same device as long as they use a different mapper
> name.
> 
> The same behavior is there in luks based volume
> 
> Also,shouldnt  the error say mapper name since the check is on the
> mapper,not the device behind the mapper.
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

The default behaviour is to forbid it. As Milan said you need --shared
flag to "avoid" it.

Please check note issue 123 and Milan answer about the "safety" of
--shared use.

You shall create linear mappings under raw cryptsetup created devices
and work under this linear mappings and not with the cryptsetup raw
created one when using --shared flag.