On Thu, 2016-12-01 at 23:06 -0800, Eric Biggers wrote: > On Thu, Dec 01, 2016 at 05:47:02PM -0800, Tim Chen wrote: > > > > On Thu, 2016-12-01 at 19:00 -0500, Mikulas Patocka wrote: > > > > > > Hi > > > > > > There is a bug in mcryptd initialization. > > > > > > This is a test module that tries various hash algorithms. When you load > > > the module with "insmod test.ko 'alg=mcryptd(md5)'", the machine crashes. > > I don't think your test setup is right. The mcryptd supports only multi-buffer > > algorithm. I don't think there is such an implementation for md5. > > > > Please refer to arch/x86/crypto/sha1-mb > > multi-buffer implementation of sha1 to see the proper > > setup and usage with mcryptd. You can also run tcrypt test to > > exercise this code. > > > > Tim > No, mcryptd must not crash the kernel if it's passed the wrong algorithm. That's true. We should detect the case when mcryptd is being passed invalid argument and not crash. We'll take a look at it. Tim -- 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
