From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 4 May 2010 17:17:16 +0200 (CEST) Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o44FHErx029674 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 4 May 2010 11:17:15 -0400 Received: from [10.34.28.146] (mazybook.brq.redhat.com [10.34.28.146]) by int-mx05.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o44FHDZV023699 for ; Tue, 4 May 2010 11:17:14 -0400 Message-ID: <4BE03A79.7060805@redhat.com> Date: Tue, 04 May 2010 17:17:13 +0200 From: Milan Broz MIME-Version: 1.0 References: <20100501180640.9035E6545B3@c-in3ws--03-02.sv2.lotusliveops.com> In-Reply-To: <20100501180640.9035E6545B3@c-in3ws--03-02.sv2.lotusliveops.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [dm-crypt] SLED10 broken dm-crypt module (was Re: [ANNOUNCE] cryptsetup 1.1.1-rc1 (test release candidate)) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: dm-crypt@saout.de On 05/01/2010 08:06 PM, Si St wrote: > query_device: crypt_query_device API call > [(equal) ,query_device:299] crypt_query_device(&co) == 0 > [(equal) ,query_device:302] crypt_query_device(&co) == 1 > [(success),query_device:304] strncmp(crypt_get_dir(), DMDIR, 11) > [(success),query_device:305] strcmp(co.cipher, "aes-cbc-essiv:sha256") > FAIL line 305 [query_device]: code 1, > FAIL: api-test For the archive: this fail is because SLED10 (2.6.16.60-0.21-default kernel) contains broken dm-crypt module. It seems this upstream patch is missing http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=37af6560f7978c60791b5f3df17ce8b3e97f2d6e it causes device-mapper table status to incorrectly prints cipher this way: 0 65536 crypt cbc(aes)-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 7:0 0 The correct form is 0 65536 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 7:0 0 So cryptsetup cannot work properly with this kernel. Milan