On Fri, 2012-06-15 at 00:15 +0300, Emmanuel Grumbach wrote:
> commit d6ee27eb13beab94056e0de52d81220058ca2297 upstream.
> 
> When we remove a key, we put a key index which was supposed
> to tell the fw that we are actually removing the key. But
> instead the fw took that index as a valid index and messed
> up the SRAM of the device.
> 
> This memory corruption on the device mangled the data of
> the SCD. The impact on the user is that SCD queue 2 got
> stuck after having removed keys.
> The message is the log that was printed is:
> 
> Queue 2 stuck for 10000ms
> 
> This doesn't seem to fix the higher queues that get stuck
> from time to time.
[...]

Queued up for 3.2.y, thanks.

Ben.

-- 
Ben Hutchings
Time is nature's way of making sure that everything doesn't happen at once.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to