crypto stuff broken in -mm?
From: Johannes Weiner
Date: Sun Jul 20 2008 - 13:25:28 EST
I can not access my encrypted partitions with -mm while they work with
For both trees I have similar configs, I didn't change anything relative
to this subsystem:
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
# 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
(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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/