From: Dominic Curran <dominic.curran@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen: Fix a grant table resource leak
Date: Fri, 11 May 2012 15:55:19 +0100 [thread overview]
Message-ID: <4FAD2857.3070107@citrix.com> (raw)
In-Reply-To: <4FAD3E8D0200007800083110@nat28.tlf.novell.com>
On 11/05/12 15:30, Jan Beulich wrote:
>>>> On 11.05.12 at 16:20, Dominic Curran<dominic.curran@citrix.com> wrote:
>> From: Dominic Curran<dominic.curran@citrix.com>
>> Date: Fri, 11 May 2012 12:24:42 +0100
>> Subject: [PATCH] xen: Fix a grant table resource leak
>>
>> If the resource (my testing shows an object in TX/RX ring) still has a
>> reference held on it, then add to a list and kick-off a timer to try
>> and free later.
> Did you see
>
> http://lists.xen.org/archives/html/xen-devel/2012-04/msg00406.html
>
> Jan
Oh!
prev parent reply other threads:[~2012-05-11 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 14:20 [PATCH] xen: Fix a grant table resource leak Dominic Curran
2012-05-11 14:30 ` Jan Beulich
2012-05-11 14:30 ` Konrad Rzeszutek Wilk
2012-05-11 14:55 ` Dominic Curran [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=4FAD2857.3070107@citrix.com \
--to=dominic.curran@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/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).