Your message dated Tue, 27 Dec 2005 10:02:12 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#344313: fixed in cryptsetup 20050111-5
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 21 Dec 2005 18:00:58 +0000
>From [EMAIL PROTECTED] Wed Dec 21 10:00:58 2005
Return-path: <[EMAIL PROTECTED]>
Received: from gozer.dminteractive.com ([66.18.16.178] ident=postfix)
by spohr.debian.org with esmtp (Exim 4.50)
id 1Ep89X-0001Tg-Gt
for [EMAIL PROTECTED]; Wed, 21 Dec 2005 09:53:27 -0800
Received: by gozer.dminteractive.com (Postfix, from userid 1000)
id 06F811E89B; Wed, 21 Dec 2005 11:53:26 -0600 (CST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Mike Hokenson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: cryptsetup: unable to create map with libdevmapper1.02
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.18
Date: Wed, 21 Dec 2005 11:53:25 -0600
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
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
---------------------------------------
Received: (at 344313-close) by bugs.debian.org; 27 Dec 2005 18:10:59 +0000
>From [EMAIL PROTECTED] Tue Dec 27 10:10:59 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1ErJ9I-0006bu-SW; Tue, 27 Dec 2005 10:02:12 -0800
From: Jonas Meurer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#344313: fixed in cryptsetup 20050111-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 27 Dec 2005 10:02:12 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2
Source: cryptsetup
Source-Version: 20050111-5
We believe that the bug you reported is fixed in the latest version of
cryptsetup, which is due to be installed in the Debian FTP archive:
cryptsetup_20050111-5.diff.gz
to pool/main/c/cryptsetup/cryptsetup_20050111-5.diff.gz
cryptsetup_20050111-5.dsc
to pool/main/c/cryptsetup/cryptsetup_20050111-5.dsc
cryptsetup_20050111-5_i386.deb
to pool/main/c/cryptsetup/cryptsetup_20050111-5_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Meurer <[EMAIL PROTECTED]> (supplier of updated cryptsetup package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 27 Dec 2005 17:55:16 +0100
Source: cryptsetup
Binary: cryptsetup
Architecture: source i386
Version: 20050111-5
Distribution: unstable
Urgency: low
Maintainer: Debian Cryptsetup Team <[EMAIL PROTECTED]>
Changed-By: Jonas Meurer <[EMAIL PROTECTED]>
Description:
cryptsetup - configures encrypted block devices
Closes: 341606 344313
Changes:
cryptsetup (20050111-5) unstable; urgency=low
.
* Redirect output of update-rc.d to /dev/null
* Create lintian override, no need for libcryptsetup{0,-dev} packages
* fix a minor typo in the cryptsetup manpage
* rebuild against new libdevmapper packages (closes: #341606)
* patch lib/libdevmapper.c, thanks to Bastian Blank for the patch.
(closes: #344313)
* add dpatch build-dependency
Files:
bfff4d06ff387ea9196682a49fbe86c8 831 admin optional cryptsetup_20050111-5.dsc
d9ea867cb9f8e4a3c50df04c162f1e32 22542 admin optional
cryptsetup_20050111-5.diff.gz
3537e4978393c5924086e652531605b6 198740 admin optional
cryptsetup_20050111-5_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDsXn6d6lUs+JfIQIRAnP+AJ0cT/GyfAW8G2bhxnJ1v+h3Ze6qFQCdExMx
yhC2XsSpLmFESqtdOmFCGts=
=cyQc
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
