From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Stotland, Inga" <inga.stotland@intel.com>
Cc: "michal.lowas-rzechonek@silvair.com"
<michal.lowas-rzechonek@silvair.com>
Subject: Re: [PATCH BlueZ] mesh: Fix clean up of node's DBUS assosiated resources
Date: Thu, 4 Jul 2019 00:16:39 +0000 [thread overview]
Message-ID: <1562199398.23933.40.camel@intel.com> (raw)
In-Reply-To: <20190703230244.20229-1-inga.stotland@intel.com>
Ap[plied
On Wed, 2019-07-03 at 16:02 -0700, Inga Stotland wrote:
> This consolidates multiple places where node's object paths,
> interfaces, etc. are de-allocated, into one routine:
> free_node_dbus_resources().
> This also addresses memory leaks assosiated with inconsistent freeing
> of object path strings.
> ---
> mesh/node.c | 66 +++++++++++++++++++++++------------------------------
> 1 file changed, 29 insertions(+), 37 deletions(-)
>
> diff --git a/mesh/node.c b/mesh/node.c
> index adc2aa93e..67e0dd014 100644
> --- a/mesh/node.c
> +++ b/mesh/node.c
> @@ -226,34 +226,46 @@ static void element_free(void *data)
> l_free(element);
> }
>
> -static void free_node_resources(void *data)
> +static void free_node_dbus_resources(struct mesh_node *node)
> {
> - struct mesh_node *node = data;
> + if (!node)
> + return;
>
> - /* Unregister io callbacks */
> - if (node->net)
> - mesh_net_detach(node->net);
> - mesh_net_free(node->net);
> + if (node->disc_watch) {
> + l_dbus_remove_watch(dbus_get_bus(), node->disc_watch);
> + node->disc_watch = 0;
> + }
>
> - l_queue_destroy(node->elements, element_free);
> - l_free(node->comp);
> - l_free(node->app_path);
> + l_queue_foreach(node->elements, free_element_path, NULL);
> l_free(node->owner);
> - l_free(node->node_path);
> -
> - if (node->disc_watch)
> - l_dbus_remove_watch(dbus_get_bus(), node->disc_watch);
> + node->owner = NULL;
> + l_free(node->app_path);
> + node->app_path = NULL;
>
> if (node->path) {
> l_dbus_object_remove_interface(dbus_get_bus(), node->path,
> MESH_NODE_INTERFACE);
>
> l_dbus_object_remove_interface(dbus_get_bus(), node->path,
> - MESH_MANAGEMENT_INTERFACE);
> + MESH_MANAGEMENT_INTERFACE);
> + l_free(node->path);
> + node->path = NULL;
> }
> +}
>
> - l_free(node->path);
> +static void free_node_resources(void *data)
> +{
> + struct mesh_node *node = data;
>
> + /* Unregister io callbacks */
> + if (node->net)
> + mesh_net_detach(node->net);
> + mesh_net_free(node->net);
> +
> + l_queue_destroy(node->elements, element_free);
> + l_free(node->comp);
> +
> + free_node_dbus_resources(node);
> l_free(node);
> }
>
> @@ -1033,24 +1045,9 @@ static void app_disc_cb(struct l_dbus *bus, void *user_data)
> l_info("App %s disconnected (%u)", node->owner, node->disc_watch);
>
> node->disc_watch = 0;
> -
> - l_queue_foreach(node->elements, free_element_path, NULL);
> -
> - l_free(node->owner);
> - node->owner = NULL;
> -
> - if (node->path) {
> - l_dbus_object_remove_interface(dbus_get_bus(), node->path,
> - MESH_NODE_INTERFACE);
> -
> - l_dbus_object_remove_interface(dbus_get_bus(), node->path,
> - MESH_MANAGEMENT_INTERFACE);
> - l_free(node->app_path);
> - node->app_path = NULL;
> - }
> + free_node_dbus_resources(node);
> }
>
> -
> static bool validate_model_property(struct node_element *ele,
> struct l_dbus_message_iter *property,
> uint8_t *num_models, bool vendor)
> @@ -1611,14 +1608,9 @@ fail:
> /* Handle failed Attach request */
> node_ready_func_t cb = req->cb;
>
> - l_queue_foreach(node->elements, free_element_path, NULL);
> - l_free(node->app_path);
> - node->app_path = NULL;
> + free_node_dbus_resources(node);
>
> - l_free(node->owner);
> - node->owner = NULL;
> cb(req->user_data, MESH_ERROR_FAILED, node);
> -
> } else {
> /* Handle failed Join and Create requests */
> if (node)
prev parent reply other threads:[~2019-07-04 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 23:02 [PATCH BlueZ] mesh: Fix clean up of node's DBUS assosiated resources Inga Stotland
2019-07-04 0:16 ` Gix, Brian [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=1562199398.23933.40.camel@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.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).