Description of problem: There is an x86_64 optimized assembly module for twofish, "twofish-x86_64". But when I access a twofish dm-crypt device, the module "twofish" is loaded instead of "twofish-x86_64", even though my CPU is x86_64. In comparison, if an AES dm-crypt device is used, the module "aes-x86_64" is loaded. Version-Release number of selected component (if applicable): 2.6.27.5-94.fc10.x86_64 How reproducible: Always Steps to Reproduce: 1. use a twofish encrypted dm-crypt device 2. lsmod 3. Actual results: twofish is loaded rather than twofish-x86_64 Expected results: twofish-x86_64 should be loaded Additional info:
looks like the best way to fix this is just to not build the non-x86_64 versions on 64bit kernels. I'll make the change.
Yes, that fixes it.
kernel-2.6.27.7-130.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kernel-2.6.27.7-130.fc10
kernel-2.6.27.7-134.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.