All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH] dbus: Fix read after free during cleanup
Date: Thu, 11 Feb 2016 13:50:25 -0600	[thread overview]
Message-ID: <56BCE601.9050308@gmail.com> (raw)
In-Reply-To: <1455101156-3587-1-git-send-email-andrew.zaborowski@intel.com>

[-- Attachment #1: Type: text/plain, Size: 350 bytes --]

Hi Andrew,

On 02/10/2016 04:45 AM, Andrew Zaborowski wrote:
> subtree_free will be checking if interfaces of objects being freed have
> a destroy callback so the interfaces should not be freed before that.
> ---
>   ell/dbus-service.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>

Applied, thanks.

Regards,
-Denis


      parent reply	other threads:[~2016-02-11 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 10:45 [PATCH] dbus: Fix read after free during cleanup Andrew Zaborowski
2016-02-10 10:45 ` [PATCH 1/9] dbus: Message builder function to copy from an iter Andrew Zaborowski
2016-02-11 19:50   ` Denis Kenzior
2016-02-10 10:45 ` [PATCH 2/9] dbus: Private function to retrieve the tree for a connection Andrew Zaborowski
2016-02-10 10:45 ` [PATCH 3/9] dbus: setters and getters API for properties Andrew Zaborowski
2016-02-10 10:45 ` [PATCH 4/9] dbus: Separate interface registration from instantiation Andrew Zaborowski
2016-02-11 19:52   ` Denis Kenzior
2016-02-10 10:45 ` [PATCH 5/9] dbus: Handle legacy GetProperties and SetProperty automatically Andrew Zaborowski
2016-02-10 10:45 ` [PATCH 6/9] dbus: Implement org.freedesktop.DBus.Properties Andrew Zaborowski
2016-02-10 10:45 ` [PATCH 7/9] dbus: Implement org.freedesktop.DBus.ObjectManager Andrew Zaborowski
2016-02-10 10:45 ` [PATCH 8/9] examples: update dbus-service to new API Andrew Zaborowski
2016-02-10 10:45 ` [PATCH 9/9] test: update to new dbus API Andrew Zaborowski
2016-02-11 19:50 ` Denis Kenzior [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=56BCE601.9050308@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ell@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.