From: Juergen Gross <jgross@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
konrad.wilk@oracle.com, netwiz@crc.id.au
Subject: Re: [PATCH 0/3] xen/blkback: several fixes of resource management
Date: Thu, 18 May 2017 17:04:18 +0200 [thread overview]
Message-ID: <bd062fe4-9d62-25ab-42f7-8d5d64c7a19b@suse.com> (raw)
In-Reply-To: <20170518143831.x5ynvb6h4a7uxk4z@MacBook-Pro-de-Roger.local>
On 18/05/17 16:38, Roger Pau Monné wrote:
> On Tue, May 16, 2017 at 08:23:17AM +0200, Juergen Gross wrote:
>> Destroying a Xen guest domain while it was doing I/Os via xen-blkback
>> leaked several resources, including references of the guest's memory
>> pages.
>>
>> This patch series addresses those leaks by correcting usage of
>> reference counts and the sequence when to free which resource.
>>
>> The series applies on top of commit 2d4456c73a487abe ("block:
>> xen-blkback: add null check to avoid null pointer dereference") in
>> Jens Axboe's tree kernel/git/axboe/linux-block.git
>>
>> Juergen Gross (3):
>> xen/blkback: fix disconnect while I/Os in flight
>> xen/blkback: don't free be structure too early
>> xen/blkback: don't use xen_blkif_get() in xen-blkback kthread
>
> All 3:
>
> Acked-by: Roger Pau Monné <roger.pau@citrix.com>
>
> The comment reported by Dietmar in patch #1 would be nice to fix.
Okay, I'll send V2 soon.
Juergen
prev parent reply other threads:[~2017-05-18 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 6:23 [PATCH 0/3] xen/blkback: several fixes of resource management Juergen Gross
2017-05-16 6:23 ` [PATCH 1/3] xen/blkback: fix disconnect while I/Os in flight Juergen Gross
2017-05-16 9:28 ` [Xen-devel] " Dietmar Hahn
2017-05-16 6:23 ` [PATCH 2/3] xen/blkback: don't free be structure too early Juergen Gross
2017-05-16 6:23 ` [PATCH 3/3] xen/blkback: don't use xen_blkif_get() in xen-blkback kthread Juergen Gross
2017-05-18 1:55 ` [PATCH 0/3] xen/blkback: several fixes of resource management Steven Haigh
2017-05-18 14:38 ` Roger Pau Monné
2017-05-18 15:04 ` Juergen Gross [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=bd062fe4-9d62-25ab-42f7-8d5d64c7a19b@suse.com \
--to=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netwiz@crc.id.au \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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