From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Yang Zhang <yang.z.zhang@intel.com>,
Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Kevin Tian <kevin.tian@intel.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] dmar: Fix double free in error paths following c/s a8bc99b
Date: Thu, 16 Jul 2015 14:22:06 +0100 [thread overview]
Message-ID: <55A7CC1E0200007800091EB0@mail.emea.novell.com> (raw)
In-Reply-To: <1437047823-24686-1-git-send-email-andrew.cooper3@citrix.com>
>>> On 16.07.15 at 13:57, <andrew.cooper3@citrix.com> wrote:
> Several error paths would end up freeing scope->devices twice.
Of course it depends how you count, but I can spot exactly one
broken case - in acpi_parse_dev_scope(). All other callers of
scope_devices_free() free the container right afterwards afaics.
Jan
next prev parent reply other threads:[~2015-07-16 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 11:57 [PATCH] dmar: Fix double free in error paths following c/s a8bc99b Andrew Cooper
2015-07-16 13:22 ` Jan Beulich [this message]
2015-07-20 1:31 ` Tian, Kevin
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=55A7CC1E0200007800091EB0@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=elena.ufimtseva@oracle.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.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).