Hello, On Mon, Feb 20, 2006 at 10:32:33AM +0100, Olivier Berger wrote: > Package: loop-aes-2.6.15-1-686 > Version: 3.1c+2 > Severity: important > > Running tests fails with stock testing kernel 2.6.15-1-686 : > > # /usr/share/loop-aes-2.6.15-1-686/runtests > dd if=/dev/zero of=test-file1 bs=1024 count=33 > 33+0 enregistrements lus. > 33+0 enregistrements écrits. > 33792 bytes transferred in 0,053852 seconds (627496 bytes/sec) > cp test-file1 test-file3 > echo 09876543210987654321 | /sbin/losetup -p 0 -e AES128 /dev/loop7 test-file3 > ioctl: LOOP_SET_STATUS: Argument invalide, requested cipher or key length > (128 bits) not supported by kernel > make: *** [tests] Erreur 1
This usually indicates that the loaded loop module is not from loop-AES, but the standard loop.ko from the kernel. This could be because loop was already loaded before loop-AES was installed, or because of some bug - let's find out which. If you do "rmmod loop; modprobe loop" and run the tests again, do they still fail? Can you send the output of lsmod after the tests have run? If the tests run OK after reloading the loop module, this is probably no bug, but to make sure you could try to verify that tests still run OK after reboot. cheers, Max
