From: Igor Druzhinin <igor.druzhinin@citrix.com>
To: wei.liu2@citrix.com
Cc: xen-devel@lists.xenproject.org,
Igor Druzhinin <igor.druzhinin@citrix.com>,
Paul.Durrant@citrix.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: [PATCH v2 1/2] xen-netback: fix memory leaks on XenBus disconnect
Date: Tue, 17 Jan 2017 20:49:37 +0000 [thread overview]
Message-ID: <1484686178-76959-2-git-send-email-igor.druzhinin@citrix.com> (raw)
In-Reply-To: <1484686178-76959-1-git-send-email-igor.druzhinin@citrix.com>
Eliminate memory leaks introduced several years ago by cleaning the
queue resources which are allocated on XenBus connection event. Namely, queue
structure array and pages used for IO rings.
Signed-off-by: Igor Druzhinin <igor.druzhinin@citrix.com>
---
drivers/net/xen-netback/xenbus.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/net/xen-netback/xenbus.c b/drivers/net/xen-netback/xenbus.c
index 6c57b02..3e99071 100644
--- a/drivers/net/xen-netback/xenbus.c
+++ b/drivers/net/xen-netback/xenbus.c
@@ -493,11 +493,20 @@ static int backend_create_xenvif(struct backend_info *be)
static void backend_disconnect(struct backend_info *be)
{
if (be->vif) {
+ unsigned int queue_index;
+
xen_unregister_watchers(be->vif);
#ifdef CONFIG_DEBUG_FS
xenvif_debugfs_delif(be->vif);
#endif /* CONFIG_DEBUG_FS */
xenvif_disconnect_data(be->vif);
+ for (queue_index = 0; queue_index < be->vif->num_queues; ++queue_index)
+ xenvif_deinit_queue(&be->vif->queues[queue_index]);
+
+ vfree(be->vif->queues);
+ be->vif->num_queues = 0;
+ be->vif->queues = NULL;
+
xenvif_disconnect_ctrl(be->vif);
}
}
@@ -1026,6 +1035,8 @@ static void connect(struct backend_info *be)
err:
if (be->vif->num_queues > 0)
xenvif_disconnect_data(be->vif); /* Clean up existing queues */
+ for (queue_index = 0; queue_index < be->vif->num_queues; ++queue_index)
+ xenvif_deinit_queue(&be->vif->queues[queue_index]);
vfree(be->vif->queues);
be->vif->queues = NULL;
be->vif->num_queues = 0;
--
1.8.3.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next parent reply other threads:[~2017-01-17 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1484686178-76959-1-git-send-email-igor.druzhinin@citrix.com>
2017-01-17 20:49 ` Igor Druzhinin [this message]
2017-01-18 9:27 ` [PATCH v2 1/2] xen-netback: fix memory leaks on XenBus disconnect Paul Durrant
2017-01-18 9:45 ` Wei Liu
2017-01-17 20:49 ` [PATCH v2 2/2] xen-netback: protect resource cleaning " Igor Druzhinin
[not found] ` <1484686178-76959-3-git-send-email-igor.druzhinin@citrix.com>
2017-01-18 9:45 ` Wei Liu
2017-01-18 9:46 ` Paul Durrant
2017-01-18 20:11 ` [PATCH v2 0/2] xen-netback: fix memory leaks " David Miller
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=1484686178-76959-2-git-send-email-igor.druzhinin@citrix.com \
--to=igor.druzhinin@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@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;
as well as URLs for NNTP newsgroup(s).