From: Keir Fraser <keir.fraser@eu.citrix.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>
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 [thread overview]
Message-ID: <C80DB652.13CE5%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <19431.60987.641218.974084@mariner.uk.xensource.com>
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
prev parent reply other threads:[~2010-05-10 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 3:22 [PATCH 2/2] reap the blktapctl thread and notify the tapdisk backend driver to release resource like memory James Song
2010-05-06 16:01 ` Ian Jackson
2010-05-07 7:20 ` Jan Beulich
2010-05-07 17:32 ` Ian Jackson
2010-05-10 7:06 ` Jan Beulich
2010-05-10 11:30 ` Ian Jackson
2010-05-10 12:10 ` Keir Fraser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C80DB652.13CE5%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=JFEHLIG@novell.com \
--cc=JSong@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.