From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: RE: Bug in tmem: refcount leak leaves zombie saved domains
Date: Fri, 11 Jun 2010 08:39:55 +0100 [thread overview]
Message-ID: <4C12046B02000078000061EA@vpn.id2.novell.com> (raw)
In-Reply-To: <6e8d71c8-6e0f-494e-8a52-d83c9a0804a2@default>
>>> On 10.06.10 at 19:54, Dan Magenheimer <dan.magenheimer@oracle.com> wrote:
> Could you give the attached a try on your test case? If
> it passes and Jan thinks it is OK (as I backed out most of
> his patch at cs 20918), then:
The combination of the two patches looks okay to me in any case;
I didn't bother checking whether 21595 alone would have been
okay too.
Jan
next prev parent reply other threads:[~2010-06-11 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 9:46 Bug in tmem: refcount leak leaves zombie saved domains Keir Fraser
2010-06-10 13:08 ` Dan Magenheimer
2010-06-10 15:38 ` Dan Magenheimer
2010-06-10 16:12 ` Keir Fraser
2010-06-10 17:54 ` Dan Magenheimer
2010-06-10 20:06 ` Keir Fraser
2010-06-10 21:43 ` Keir Fraser
2010-06-10 22:34 ` Dan Magenheimer
2010-06-11 7:39 ` Jan Beulich [this message]
2010-06-10 16:34 ` Keir Fraser
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=4C12046B02000078000061EA@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=dan.magenheimer@oracle.com \
--cc=keir.fraser@eu.citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).