From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH 2/2] reap the blktapctl thread and notify the
	tapdisk backend driver to release resource like  memory..
Date: Mon, 10 May 2010 13:10:42 +0100
Message-ID: <C80DB652.13CE5%keir.fraser@eu.citrix.com>
References: <19431.60987.641218.974084@mariner.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <19431.60987.641218.974084@mariner.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, Jan Beulich <JBeulich@novell.com>
Cc: Jim Fehlig <JFEHLIG@novell.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, James Song <JSong@novell.com>
List-Id: xen-devel@lists.xenproject.org

On 10/05/2010 12:30, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:

> Jan Beulich writes ("Re: [Xen-devel] [PATCH 2/2] reap the blktapctl thread
> and  notify the tapdisk backend driver to release resource like  memory.."):
>> The bug was with the blktap kernel driver not being able to clean up
>> after an unclean exit of qemu. [....]
> 
> This is a serious kernel bug which absolutely must be fixed.  There is
> no way the userland toolstack can promise that qemu won't just die.

Well it depends who/what sets up the tap context. Is it actually qemu, or is
the initial setup done by xend and then qemu merely plumbed into it?

 -- Keir