Hi Richard,
On 31 May 2012 18:15, Torne (Richard Coles) wrote:
> On 31 May 2012 11:00, Ulf Hansson wrote:
>> Hi Richard,
>>
>> On 29 May 2012 17:02, Torne (Richard Coles) wrote:
>>> From: "Torne (Richard Coles)"
>>>
>>> MMC CSD info can specify very large, ridiculous timeouts, big enough to
>>
On 31 May 2012 11:00, Ulf Hansson wrote:
> Hi Richard,
>
> On 29 May 2012 17:02, Torne (Richard Coles) wrote:
>> From: "Torne (Richard Coles)"
>>
>> MMC CSD info can specify very large, ridiculous timeouts, big enough to
>> overflow timeout_ns on 32-bit machines. This can result in the card
>> t
Hi Richard,
On 29 May 2012 17:02, Torne (Richard Coles) wrote:
> From: "Torne (Richard Coles)"
>
> MMC CSD info can specify very large, ridiculous timeouts, big enough to
> overflow timeout_ns on 32-bit machines. This can result in the card
> timing out on every operation because the wrapped tim
From: "Torne (Richard Coles)"
MMC CSD info can specify very large, ridiculous timeouts, big enough to
overflow timeout_ns on 32-bit machines. This can result in the card
timing out on every operation because the wrapped timeout value is far
too small.
Fix the overflow by capping the result at 2
From: "Torne (Richard Coles)"
MMC CSD info can specify very large, ridiculous timeouts, big enough to
overflow timeout_ns on 32-bit machines. This can result in the card
timing out on every operation because the wrapped timeout value is far
too small.
Fix the overflow by calculating the timeout