From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] inconsistency in opening multiple mappers on the same device
Date: Fri, 1 Jun 2012 07:55:24 +0200 [thread overview]
Message-ID: <20120601055524.GA27280@tansi.org> (raw)
In-Reply-To: <CAFnMBaTKyAy3=O5LBwFWr-chY_+Zu-tVUX7+vDAWnDah=kuc5g@mail.gmail.com>
Of course you cannot have two mappings on the same name.
The collision is not for the mapping, but for the name!
How would you even address a mapping if you had several on
the same /dev/mapper/<...> entry? That would be like
having several different files under the same file name.
Arno
On Thu, May 31, 2012 at 06:12:02PM -0400, .. 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
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-06-01 5:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 22:12 [dm-crypt] inconsistency in opening multiple mappers on the same device .. ink ..
2012-06-01 5:55 ` Arno Wagner [this message]
2012-06-01 12:47 ` .. ink ..
2012-06-01 13:00 ` Milan Broz
2012-06-01 6:31 ` Milan Broz
2012-06-01 10:52 ` Javier Juan Martínez Cabezón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120601055524.GA27280@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.