linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 6/9] Fix memory leak when loading keys
Date: Thu, 07 Jul 2011 10:35:41 +0200	[thread overview]
Message-ID: <1310027746.21109.56.camel@aeonflux> (raw)
In-Reply-To: <1309983041-23744-7-git-send-email-vinicius.gomes@openbossa.org>

Hi Vincius.

> Core bluetoothd doesn't need to have a reference to the link key list,
> so we pass a reference to the list and free it as soon as possible. If any
> user need to keep a copy of that list around, they need to copy it. This makes
> the memory management more consistent.
> ---
>  plugins/hciops.c |   14 +++++++++++++-
>  src/adapter.c    |    6 +++---
>  2 files changed, 16 insertions(+), 4 deletions(-)
> 
> diff --git a/plugins/hciops.c b/plugins/hciops.c
> index 207e187..56daf0d 100644
> --- a/plugins/hciops.c
> +++ b/plugins/hciops.c
> @@ -3450,6 +3450,7 @@ static int hciops_restore_powered(int index)
>  static int hciops_load_keys(int index, GSList *keys, gboolean debug_keys)
>  {
>  	struct dev_info *dev = &devs[index];
> +	GSList *l, *n, *new;
>  
>  	DBG("hci%d keys %d debug_keys %d", index, g_slist_length(keys),
>  								debug_keys);
> @@ -3457,7 +3458,18 @@ static int hciops_load_keys(int index, GSList *keys, gboolean debug_keys)
>  	if (dev->keys != NULL)
>  		return -EEXIST;
>  
> -	dev->keys = keys;
> +	new = g_slist_copy(keys);
> +
> +	for (n = new, l = keys; l && n; l = l->next, n = n->next) {
> +		struct link_key_info *orig;
> +
> +		orig = l->data;
> +
> +		n->data = g_malloc0(sizeof(*orig) + orig->dlen);
> +		memcpy(n->data, orig, sizeof(*orig) + orig->dlen);

you don't need to add a memset via g_malloc0 here. And do we really not
wanna check the memory allocation here?

Regards

Marcel



  reply	other threads:[~2011-07-07  8:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 20:10 [PATCH BlueZ v2 0/9] Permanent storage of SMP keys Vinicius Costa Gomes
2011-07-06 20:10 ` [PATCH BlueZ v2 1/9] Add stubs for storing " Vinicius Costa Gomes
2011-07-06 20:10 ` [PATCH BlueZ v2 2/9] Add support " Vinicius Costa Gomes
2011-07-07  8:28   ` Marcel Holtmann
2011-07-06 20:10 ` [PATCH BlueZ v2 3/9] Add support for creating the device from the " Vinicius Costa Gomes
2011-07-06 20:10 ` [PATCH BlueZ v2 4/9] Define macros for link key types Vinicius Costa Gomes
2011-07-06 20:10 ` [PATCH BlueZ v2 5/9] Fix using "magic" values for " Vinicius Costa Gomes
2011-07-06 20:10 ` [PATCH BlueZ v2 6/9] Fix memory leak when loading keys Vinicius Costa Gomes
2011-07-07  8:35   ` Marcel Holtmann [this message]
2011-07-07 11:01     ` Anderson Lizardo
2011-07-06 20:10 ` [PATCH BlueZ v2 7/9] Add support for getting the Encryption Key Size via btio Vinicius Costa Gomes
2011-07-06 20:10 ` [PATCH BlueZ v2 8/9] Add support for passing the CID to btiotest Vinicius Costa Gomes
2011-07-06 20:10 ` [PATCH BlueZ v2 9/9] Add support for btiotest to returning the key size Vinicius Costa Gomes

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=1310027746.21109.56.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vinicius.gomes@openbossa.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).