From: Johannes Weiner <hannes@saeurebad.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Subject: crypto stuff broken in -mm?
CC: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Date: Sun, 20 Jul 2008 19:24:48 +0200
Message-ID: <87ljzwh3j3.fsf@saeurebad.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1571
Lines: 50

Hi,

I can not access my encrypted partitions with -mm while they work with
mainline.

For both trees I have similar configs, I didn't change anything relative
to this subsystem:

CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_586=y

On mainline I do cryptsetup and then mount /dev/mapper/foo /mnt/foo
successfully, while I have the following behaviour on -mm:

# cryptsetup create foo /dev/sdd1
Enter passphrase:
# mount /dev/mapper/foo /mnt/foo
mount: you must specify the filesystem type
# mount -t ext3 /dev/mapper/foo /mnt/foo
mount: wrong fs type, bad option, bad superblock on /dev/mapper/foo,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
# dmesg | tail -n1
[56975.640750] VFS: Can't find ext3 filesystem on dev dm-0.
# cryptsetup --version
cryptsetup 1.0.5

(This is the only relevant info in dmesg, unfortunately).

The cipher is aes-cbc-plain, according to cryptsetup status.

It's a 32bit x86 machine.  I suspect that -next has the same problem as
-mm's crypto changes seem to come from linux-next.patch.

I am willing to try patches (and hope they won't destroy 640GB worth of
porn).

	Hannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/