On 4/23/15, 04:25, "Tim Deegan" wrote:
>At 17:44 +0100 on 16 Apr (1429206250), Tim Deegan wrote:
>> update_intremap_entry_from_msi() doesn't write to its data pointer on
>> some error paths, so we copying that variable into the msg would count
>> as undefined behaviour.
>>
>> Signed-off-by: Tim
At 17:44 +0100 on 16 Apr (1429206250), Tim Deegan wrote:
> update_intremap_entry_from_msi() doesn't write to its data pointer on
> some error paths, so we copying that variable into the msg would count
> as undefined behaviour.
>
> Signed-off-by: Tim Deegan
> Cc: Suravee Suthikulpanit
> Cc: Arav
>>> On 16.04.15 at 19:19, wrote:
> On 16/04/15 17:44, Tim Deegan wrote:
>> update_intremap_entry_from_msi() doesn't write to its data pointer on
>> some error paths, so we copying that variable into the msg would count
>> as undefined behaviour.
>>
>> Signed-off-by: Tim Deegan
>> Cc: Suravee Suth
On Thu, Apr 16, 2015 at 05:44:10PM +0100, Tim Deegan wrote:
> update_intremap_entry_from_msi() doesn't write to its data pointer on
> some error paths, so we copying that variable into the msg would count
> as undefined behaviour.
>
> Signed-off-by: Tim Deegan
> Cc: Suravee Suthikulpanit
> Cc: A
On 16/04/15 17:44, Tim Deegan wrote:
> update_intremap_entry_from_msi() doesn't write to its data pointer on
> some error paths, so we copying that variable into the msg would count
> as undefined behaviour.
>
> Signed-off-by: Tim Deegan
> Cc: Suravee Suthikulpanit
> Cc: Aravind Gopalakrishnan
