> Why you want to workaround this? It's safe to ignore hmac(crc32) warning. Because it stops from proceeding. I would have expected that modprobe tcrypt sec=1 type=1000 would have executed all test cases. Even if I just want to test one [root@amd ~]# modprobe tcrypt sec=2 type=402 ERROR: could not insert 'tcrypt': No such file or directory I get an error. -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
