Comment 223 for bug 445852

Revision history for this message
Martin Pitt (pitti) wrote :

So in summary, the problem is fixed in the lucid version of libatasmart. While the code could be a little more robust for future extensions (which I'll discuss in the upstream bug), there are currently no code paths which can lead to the situation that triggers HSM violations.