From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH] xen-blkback: defer freeing blkif to avoid blocking xenwatch Date: Mon, 12 May 2014 11:43:56 +0100 Message-ID: <5370A5EC.1010808@citrix.com> References: <1399678479-14758-1-git-send-email-vali.priescu@gmail.com> <537096D5.4090809@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Valentin Priescu Cc: xen-devel , Matt Wilson , Valentin Priescu List-Id: xen-devel@lists.xenproject.org On 12/05/14 11:41, Valentin Priescu wrote: > On Mon, May 12, 2014 at 11:39 AM, David Vrabel wrote: >> If xen_blkif_disconnect() returns -EBUSY, nothing will trigger the >> reconnect. >> > > Yeah, I should do something like: > err = xen_blkif_disconnect(be->blkif); > if (err) { > xenbus_dev_fatal(dev, err, "disconnecting %s", > dev->otherend); I think that's ok, but the error message should be "pending I/O". You don't need to include the name of the otherend in the error message. David