On tisdag 18 september 2018 kl. 01:25:29 EEST Boris Ostrovsky wrote: > On 9/17/18 5:19 PM, Jarkko Sakkinen wrote: > > Just to understand this bug better why did not the wrong version > > cause any undefined behavior? Sounds like a fatal bug. Does this > > cause crashes? > > AFAIK, no, no crashes. I haven't tested this myself (and I believe > relatively few people use this functionality, which explains why this > has not been fixed for so long) but I don't think it will necessarily > crash. It's just that the frontend driver will be reading from wrong > location, causing TPM not to function properly. I bumped my head into this last week and spent most of the week trying to figure out why the vtpm did not respond. Finally found the email from the guy that dirscovered and fixed it. Did the fix and rescompiled. Now it seems to be working fine. The patch is surprisingly 2 years old!! I will be very pleased to see it go in to the official kernel! But no crash. Just a timeout when trying to communicate with the vtpm-engine. Best Dag
