From: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
To: Szymon Janc <szymon.janc@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH_v2 1/4] profiles/health/hdp: Fix memory leak in SDP record preparati Sdp record preparation part is copied to android/health.c from profiles/health/hdp_utils.c. Memory leak is noticed while testing. Memory summay is from android daemon, but code snippet is same. It is already fixed in android/health.c while submitting android related patches.
Date: Tue, 17 Jun 2014 12:59:29 +0300 [thread overview]
Message-ID: <53A01181.1050402@linux.intel.com> (raw)
In-Reply-To: <1478681.tbExyMG8XR@uw000953>
Hi Szymon,
On 06/17/2014 12:29 PM, Szymon Janc wrote:
> Hi Ravi,
>
> On Tuesday 17 of June 2014 01:02:47 Ravi kumar Veeramally wrote:
>> ==12515== 286 (16 direct, 270 indirect) bytes in 1 blocks are definitely lost in loss record 158 of 165
>> ==12515== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
>> ==12515== by 0x44AC45: sdp_list_append (sdp.c:1743)
>> ==12515== by 0x4398F9: register_features (health.c:381)
>> ==12515== by 0x4091CC: queue_foreach (queue.c:219)
>> ==12515== by 0x43A31F: bt_health_mdep_cfg_data (health.c:398)
>> ==12515== by 0x418B50: cmd_watch_cb (ipc.c:144)
>> ==12515== by 0x4E7FCE4: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0)
>> ==12515== by 0x4E80047: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0)
>> ==12515== by 0x4E80309: g_main_loop_run (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4000.0)
>> ==12515== by 0x4044F2: main (main.c:538)
>> ---
> There is something wrong with this patch. Subject is very long. Should that be
> in commit message body?
Oops, I will correct it.
>> profiles/health/hdp_util.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/profiles/health/hdp_util.c b/profiles/health/hdp_util.c
>> index 58770b5..47c464e 100644
>> --- a/profiles/health/hdp_util.c
>> +++ b/profiles/health/hdp_util.c
>> @@ -652,6 +652,8 @@ static gboolean register_service_sup_features(GSList *app_list,
>> return FALSE;
>> }
>>
>> + sdp_list_free(sup_features, free_hdp_list);
>> +
>> return TRUE;
>> }
>>
>>
Thanks,
Ravi.
next prev parent reply other threads:[~2014-06-17 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 22:02 [PATCH_v2 0/4] Intiates L2CAP Control Channel Ravi kumar Veeramally
2014-06-16 22:02 ` [PATCH_v2 1/4] profiles/health/hdp: Fix memory leak in SDP record preparati Sdp record preparation part is copied to android/health.c from profiles/health/hdp_utils.c. Memory leak is noticed while testing. Memory summay is from android daemon, but code snippet is same. It is already fixed in android/health.c while submitting android related patches Ravi kumar Veeramally
2014-06-17 9:29 ` Szymon Janc
2014-06-17 9:59 ` Ravi kumar Veeramally [this message]
2014-06-16 22:02 ` [PATCH_v2 2/4] anrdoid/health: Fix wrong channel type defines Ravi kumar Veeramally
2014-06-17 9:29 ` Szymon Janc
2014-06-17 10:03 ` Ravi kumar Veeramally
2014-06-16 22:02 ` [PATCH_v2 3/4] android/health: Initial connect channel implementation Ravi kumar Veeramally
2014-06-17 10:16 ` Szymon Janc
2014-06-17 10:48 ` Ravi kumar Veeramally
2014-06-16 22:02 ` [PATCH_v2 4/4] android/health: Notify channel connection status Ravi kumar Veeramally
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=53A01181.1050402@linux.intel.com \
--to=ravikumar.veeramally@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon.janc@tieto.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 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.