On 2019/5/6 下午6:32, Lukas Straub wrote:
On Sat, 20 Apr 2019 19:14:25 +0200
Lukas Straub wrote:
From: Lukas Straub
Because event_unhandled_count may be accessed concurrently, it needs
to be protected by taking the lock. However the assert is outside the
lock, probably causing it to read garb
Cc'ing Paolo & Stefan
On 4/20/19 7:14 PM, Lukas Straub wrote:
> From: Lukas Straub
> Because event_unhandled_count may be accessed concurrently, it needs
> to be protected by taking the lock. However the assert is outside the
> lock, probably causing it to read garbage and aborting Qemu erroneous
On Sat, 20 Apr 2019 19:14:25 +0200
Lukas Straub wrote:
> From: Lukas Straub
> Because event_unhandled_count may be accessed concurrently, it needs
> to be protected by taking the lock. However the assert is outside the
> lock, probably causing it to read garbage and aborting Qemu
> erroneously.
> -Original Message-
> From: Lukas Straub [mailto:lukasstra...@web.de]
> Sent: Sunday, April 21, 2019 1:14 AM
> To: qemu-devel@nongnu.org
> Cc: Zhang, Chen
> Subject: [PATCH v2] net/colo-compare.c: Fix a crash in COLO Primary.
>
> From: Lukas Straub Because event_unhandled_count
> may
On 4/20/19 7:14 PM, Lukas Straub wrote:
> From: Lukas Straub
> Because event_unhandled_count may be accessed concurrently, it needs
> to be protected by taking the lock. However the assert is outside the
> lock, probably causing it to read garbage and aborting Qemu erroneously.
>
> The Bug only h
From: Lukas Straub
Because event_unhandled_count may be accessed concurrently, it needs
to be protected by taking the lock. However the assert is outside the
lock, probably causing it to read garbage and aborting Qemu erroneously.
The Bug only happens when running Qemu in COLO mode.
This Patch f
