public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 4/4] Fix leak of EIR data if RSSI does not change
Date: Mon, 27 Dec 2010 17:11:22 +0200	[thread overview]
Message-ID: <20101227151122.GD17203@jh-x301> (raw)
In-Reply-To: <1293456068-11615-4-git-send-email-anderson.lizardo@openbossa.org>

Hi Lizardo,

On Mon, Dec 27, 2010, Anderson Lizardo wrote:
> --- a/src/event.c
> +++ b/src/event.c
> @@ -452,9 +452,13 @@ void btd_event_advertising_report(bdaddr_t *local, le_advertising_info *info)
>  
>  	rssi = *(info->data + info->length);
>  
> -	adapter_update_device_from_info(adapter, info->bdaddr, rssi,
> +	if (!adapter_update_device_from_info(adapter, info->bdaddr, rssi,
>  					info->evt_type, eir_data.name,
> -					eir_data.services, eir_data.flags);
> +					eir_data.services, eir_data.flags)) {
> +		g_slist_foreach(eir_data.services, (GFunc) g_free, NULL);
> +		g_slist_free(eir_data.services);
> +		g_free(eir_data.name);
> +	}
>  }
>  
>  static void update_lastseen(bdaddr_t *sba, bdaddr_t *dba)
> @@ -556,8 +560,12 @@ void btd_event_device_found(bdaddr_t *local, bdaddr_t *peer, uint32_t class,
>  	} else if (eir_data.name != NULL)
>  		g_free(eir_data.name);
>  
> -	adapter_update_found_devices(adapter, peer, rssi, class, name, alias,
> -					legacy, eir_data.services, name_status);
> +	if (!adapter_update_found_devices(adapter, peer, rssi, class, name,
> +					alias, legacy, eir_data.services,
> +					name_status)) {
> +		g_slist_foreach(eir_data.services, (GFunc) g_free, NULL);
> +		g_slist_free(eir_data.services);
> +	}
>  
>  	g_free(name);
>  	g_free(alias);

In general this seems fine, but to avoid future memory leaks in case you
go ahead and change the eir_data struct wouldn't it be better to have a
separate free_eir_data() function which does the g_slist_foreach,
g_slist_free and g_free?

Johan

  reply	other threads:[~2010-12-27 15:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 13:21 [PATCH 1/4] Remove ancient NAME_SENT name resolution status Anderson Lizardo
2010-12-27 13:21 ` [PATCH 2/4] Use stored device name (if any) instead of EIR data Anderson Lizardo
2010-12-27 14:14   ` Luiz Augusto von Dentz
2010-12-27 14:35     ` Anderson Lizardo
2010-12-27 14:53       ` Johan Hedberg
2010-12-27 15:33         ` Anderson Lizardo
2010-12-27 15:21       ` Anderson Lizardo
2010-12-27 18:20   ` Anderson Lizardo
2010-12-27 13:21 ` [PATCH 3/4] Remove outdated comments Anderson Lizardo
2010-12-27 15:09   ` Johan Hedberg
2010-12-27 13:21 ` [PATCH 4/4] Fix leak of EIR data if RSSI does not change Anderson Lizardo
2010-12-27 15:11   ` Johan Hedberg [this message]
2010-12-27 18:23     ` Anderson Lizardo
2010-12-27 18:17   ` [PATCH v2] " Anderson Lizardo
2010-12-27 21:48     ` Johan Hedberg
2010-12-27 22:24       ` Anderson Lizardo
2010-12-28 18:16         ` Anderson Lizardo
2010-12-28 18:10     ` [PATCH v3] " Anderson Lizardo
2010-12-28 18:49       ` Johan Hedberg
2010-12-27 15:08 ` [PATCH 1/4] Remove ancient NAME_SENT name resolution status Johan Hedberg

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=20101227151122.GD17203@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=anderson.lizardo@openbossa.org \
    --cc=linux-bluetooth@vger.kernel.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