From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35064) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aj1bn-0003cb-H1 for qemu-devel@nongnu.org; Thu, 24 Mar 2016 05:31:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aj1bl-0007n5-BT for qemu-devel@nongnu.org; Thu, 24 Mar 2016 05:31:15 -0400 Received: from e06smtp06.uk.ibm.com ([195.75.94.102]:49452) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aj1bl-0007mY-23 for qemu-devel@nongnu.org; Thu, 24 Mar 2016 05:31:13 -0400 Received: from localhost by e06smtp06.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 24 Mar 2016 09:31:09 -0000 Date: Thu, 24 Mar 2016 10:31:00 +0100 From: Cornelia Huck Message-ID: <20160324103100.052c229f.cornelia.huck@de.ibm.com> In-Reply-To: <20160324094756.460d6dff.cornelia.huck@de.ibm.com> References: <1458123018-18651-1-git-send-email-famz@redhat.com> <1458123018-18651-5-git-send-email-famz@redhat.com> <20160317150057.GP14062@stefanha-x1.localdomain> <56EAC82A.50907@redhat.com> <20160322125254.GB9749@ad.usersys.redhat.com> <56F18955.4060005@redhat.com> <20160323091009.64eb4cd8.cornelia.huck@de.ibm.com> <56F25D23.5070604@redhat.com> <56F25E0B.2000105@de.ibm.com> <56F3A31D.5000609@linux.vnet.ibm.com> <20160324093230.5a88cd0f.cornelia.huck@de.ibm.com> <20160324094756.460d6dff.cornelia.huck@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 4/4] virtio-blk: Clean up start/stop with mutex and BH List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Kevin Wolf , Fam Zheng , qemu-block@nongnu.org, Christian Borntraeger , Stefan Hajnoczi , "Michael S. Tsirkin" , tu bo , Stefan Hajnoczi , Paolo Bonzini On Thu, 24 Mar 2016 09:47:56 +0100 Cornelia Huck wrote: > On Thu, 24 Mar 2016 09:32:30 +0100 > Cornelia Huck wrote: > > > I'll re-send my patches with some added interface doc in patch 1. Stay > > tuned. > > Grr. Unfortunately, this fails for _me_ now (-EEXIST after reboot). > Debugging. Good news is that I think I understand what happens. Bad news is that we can scratch all of the previous testing :( My patchset had a typo (check for !disabled instead of disabled). After I fixed that, the second assignment of the ioeventfd started failing (that's what changed when I started passing assign in stop_ioeventfd) with -EEXIST as the previous ioeventfd is of course still assigned. What we actually want is to keep the ioeventfd assigned, not add a new one. But we still want adding a new ioeventfd to fail in case of collisions. I think we need to track whether we already assigned an ioeventfd and don't re-register in that case. I'll try to cook something up.