[Pkg-cryptsetup-devel] Bug#344313: cryptsetup: unable to create map with libdevmapper1.02

[Mike Hokenson]

Package: cryptsetup
Version: 20050111-4+b1
Severity: grave
Justification: renders package unusable


After last nights upgrade to cryptsetup 20050111-4+b1, I'm unable to map new or existing devices. Only by relinking to libdevmapper1.01 does it work.

gozer:/tmp# dd if=/dev/zero of=test bs=1M count=4
4+0 records in
4+0 records out
4194304 bytes (4.2 MB) copied, 0.047132 seconds, 89.0 MB/s
gozer:/tmp# losetup /dev/loop0 test
gozer:/tmp# cryptsetup create test /dev/loop0
Command failed: Invalid argument

gozer:/tmp# ./cryptsetup-1.01 create test /dev/loop0
Enter passphrase: 

A strace between the two look similar, but when cryptsetup should open the device and prompt for the passphrase, it errors out.

# 1.02
8658  open("/proc/misc", O_RDONLY|O_LARGEFILE) = 3
8658  fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
8658  mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40017000
8658  read(3, " 63 device-mapper\n  1 psaux\n175 "..., 1024) = 48
8658  close(3)                          = 0
8658  munmap(0x40017000, 4096)          = 0
8658  stat64("/dev/mapper/control", {st_mode=S_IFCHR|0600, st_rdev=makedev(10, 63), ...}) = 0
8658  open("/dev/mapper/control", O_RDWR|O_LARGEFILE) = 3
8658  open("/proc/devices", O_RDONLY|O_LARGEFILE) = 4
8658  fstat64(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
8658  mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40017000
8658  read(4, "Character devices:\n  1 mem\n  2 p"..., 1024) = 424
8658  read(4, "", 1024)                 = 0
8658  close(4)                          = 0
8658  munmap(0x40017000, 4096)          = 0
8658  ioctl(3, DM_VERSION, 0x8096548)   = 0
8658  ioctl(3, DM_TABLE_STATUS, 0x8096548) = -1 ENXIO (No such device or address)
8658  close(3)                          = 0
8658  write(2, "Command failed", 14)    = 14
8658  write(2, ": Invalid argument\n", 19) = 19
8658  exit_group(1)                     = ?

# 1.01
8870  stat64("/dev/mapper/control", {st_mode=S_IFCHR|0600, st_rdev=makedev(10, 63), ...}) = 0
8870  open("/dev/mapper/control", O_RDWR|O_LARGEFILE) = 3
8870  ioctl(3, DM_VERSION, 0x804e328)   = 0
8870  ioctl(3, DM_TABLE_STATUS, 0x804e2e8) = -1 ENXIO (No such device or address)
8870  open("/dev/loop0", O_RDONLY|O_LARGEFILE) = 4
8870  ioctl(4, BLKGETSIZE64, 0xbfa35f10) = 0
8870  close(4)                          = 0
8870  ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
8870  open("/dev/tty", O_RDWR|O_CREAT|O_TRUNC, 0666) = 4

I found a similar report <http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/1312> on the dm-crypt mailing list, but noone responded and he said crtypsetup mysteriously started working at a later date.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages cryptsetup depends on:
ii  dmsetup                      2:1.02.02-1 The Linux Kernel Device Mapper use
ii  libc6                        2.3.5-9     GNU C Library: Shared libraries an
ii  libdevmapper1.02             2:1.02.02-1 The Linux Kernel Device Mapper use
ii  libgcrypt11                  1.2.2-1     LGPL Crypto library - runtime libr
ii  libgpg-error0                1.1-4       library for common error values an
ii  libpopt0                     1.7-5       lib for parsing cmdline parameters

cryptsetup recommends no packages.

-- no debconf information