From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51442) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fONHp-00049N-BE for qemu-devel@nongnu.org; Thu, 31 May 2018 09:06:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fONHk-0001zl-Py for qemu-devel@nongnu.org; Thu, 31 May 2018 09:06:37 -0400 Sender: =?UTF-8?Q?Philippe_Mathieu=2DDaud=C3=A9?= References: <20180531004323.4611-1-jsnow@redhat.com> <5B0FE8AD020000480007AD4C@prv-mh.provo.novell.com> From: =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= Message-ID: <73ed37d7-2d75-0ae6-c2c4-c75ce59e68fc@amsat.org> Date: Thu, 31 May 2018 10:06:28 -0300 MIME-Version: 1.0 In-Reply-To: <5B0FE8AD020000480007AD4C@prv-mh.provo.novell.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH 0/3] ahci: fix completion race condition List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bruce Rogers , "qemu-block@nongnu.org" , qemu-devel@nongnu.org, jsnow@redhat.com Hi Bruce, On 05/31/2018 09:21 AM, Bruce Rogers wrote: >>>> On 5/30/2018 at 6:43 PM, John Snow wrote: >> Commit d759c951f changed the main thread lock release/reacquisition, >> and in so doing apparently jostled loose a race condition in the AHCI >> code. >> >> Patch 2 should be sufficient to fix this, and patches 1 and 3 are just >> little trivial fixes. >> >> This might be sufficient to fix the bug as reported at >> https://bugs.launchpad.net/qemu/+bug/1769189 >> but the nature of the timing changes make it difficult to confirm, >> so I am posting this patchset for the reporters to help test. >> >> John Snow (3): >> ahci: trim signatures on raise/lower >> ahci: fix PxCI register race >> ahci: don't schedule unnecessary BH >> >> hw/ide/ahci.c | 24 +++++++++++‑‑‑‑‑‑‑‑‑‑‑‑‑ >> 1 file changed, 11 insertions(+), 13 deletions(‑) >> >> ‑‑ >> 2.14.3 > > In my case, I applied these 3 patches on top of v2.12 qemu under which > I can fairly reliably reproduce Windows10 disk delays. With these patches, > after quite a number of attempts, I no longer can reproduce the failure > case, so from my perspective it solves the issue. Does that implicitly mean John can use your "Tested-by: Bruce Rogers " tag?