From: Paul Durrant <paul.durrant@citrix.com>
To: netdev@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH net 0/2] xen-netback: update memory leak fix to avoid BUG
Date: Thu, 2 Mar 2017 12:54:24 +0000 [thread overview]
Message-ID: <1488459266-29269-1-git-send-email-paul.durrant@citrix.com> (raw)
Commit 9a6cdf52b85e "xen-netback: fix memory leaks on XenBus disconnect"
added missing code to fix a memory leak by calling vfree() in the
appropriate place.
Unfortunately subsequent commit f16f1df65f1c "xen-netback: protect
resource cleaning on XenBus disconnect" then wrapped this call to vfree()
in a spin lock, leading to a BUG due to incorrect context.
Patch #1 makes the existing code more readable
Patch #2 fixes the problem
Paul Durrant (2):
xen-netback: keep a local pointer for vif in backend_disconnect()
xen-netback: don't vfree() queues under spinlock
drivers/net/xen-netback/xenbus.c | 31 +++++++++++++++++++------------
1 file changed, 19 insertions(+), 12 deletions(-)
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-03-02 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 12:54 Paul Durrant [this message]
2017-03-02 12:54 ` [PATCH net 1/2] xen-netback: keep a local pointer for vif in backend_disconnect() Paul Durrant
2017-03-02 13:35 ` Wei Liu
2017-03-02 12:54 ` [PATCH net 2/2] xen-netback: don't vfree() queues under spinlock Paul Durrant
2017-03-02 13:23 ` Juergen Gross
2017-03-02 13:35 ` Wei Liu
2017-03-03 17:36 ` [PATCH net 0/2] xen-netback: update memory leak fix to avoid BUG 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=1488459266-29269-1-git-send-email-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--cc=netdev@vger.kernel.org \
--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).