[Lucid] [Regression] crypsetup leaves temporary-cryptsetup-nnnn files lying around in /dev/mapper/

Bug #580456 reported by Swâmi Petaramesh
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: cryptsetup

Looks like a bug that existed looooong ago (2007/11, bug #162582 ) and that had been fixed loooooong ago has reappeared in Lucid since a couple weeks (hint : latest updates...)

Same description as in the far away past : « In some situations (I could not yet clearly determine in which exact conditions this happens (*) ), after running cryptsetup, a device /dev/mapper/temporary-cryptsetup-[0-9]+ (pidnum ?) is left lying around. »

(*) "cryptsetup luksOpen" is a good candidate for ending with temp things lying around.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: cryptsetup 2:1.1.0~rc2-1ubuntu13
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Fri May 14 13:01:24 2010
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: cryptsetup
crypttab:
 # <target name> <source device> <key file> <options>
 c_VG1 /dev/sda6 UUID=524d4883-5fcd-427e-8b7f-61b1ab88aea8:.fnix.rootkey.bin luks,tries=1,keyscript=/usr/local/sbin/bootkeyscript
 #c_VG1 /dev/sda6 none luks,tries=3

Revision history for this message
Swâmi Petaramesh (swami-petaramesh) wrote :
Revision history for this message
asi (gmazyland) wrote :

Just to verify that internal cryptsetup "defense" against broken udev rules work at least:

Can you post here output of "dmsetup table" of that orphaned temportary-cryptsetup-* device?
(It should be already replaced by error segment to prevent keyslot access.)

Revision history for this message
Swâmi Petaramesh (swami-petaramesh) wrote :

@asi :

# ls -l /dev/mapper currenty shows a :

brw-rw---- 1 root disk 252, 9 2010-05-14 12:50 temporary-cryptsetup-6104

...where...:

# cryptsetup status temporary-cryptsetup-6104
/dev/mapper/temporary-cryptsetup-6104 is inactive.

...and...:

# dmsetup table
...doesn't show any entry relating to "temporary-cryptsetup-6104"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.