From: Szymon Janc <szymon.janc@tieto.com>
To: Atul Rai <a.rai@samsung.com>
Cc: linux-bluetooth@vger.kernel.org, sachin.dev@samsung.com
Subject: Re: [PATCH v3] android/client: Fix memory leak while using realloc()
Date: Wed, 29 Jul 2015 00:29:01 -0700 (PDT) [thread overview]
Message-ID: <32687193.BbdPDPfzcv@leonov> (raw)
In-Reply-To: <1438057250-17977-1-git-send-email-a.rai@samsung.com>
Hi Atul,
On Tuesday 28 of July 2015 09:50:50 Atul Rai wrote:
> While reallocating space to store additional "remote device set" using
> realloc, if realloc() fails, the original block is left untouched but
> reference to that block is lost as NULL is assigned to remote_devices.
> The original block needs to be freed before return.
> ---
> android/client/if-bt.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/android/client/if-bt.c b/android/client/if-bt.c
> index 4723024..c9acf6c 100644
> --- a/android/client/if-bt.c
> +++ b/android/client/if-bt.c
> @@ -118,10 +118,19 @@ void add_remote_device(const bt_bdaddr_t *addr)
>
> /* Realloc space if needed */
> if (remote_devices_cnt >= remote_devices_capacity) {
> + bt_bdaddr_t *tmp;
> +
> remote_devices_capacity *= 2;
> + /*
> + * Save reference to previously allocated memory block so that
> + * it can be freed in case realloc fails.
> + */
> + tmp = remote_devices;
> +
> remote_devices = realloc(remote_devices, sizeof(bt_bdaddr_t) *
> remote_devices_capacity);
> if (remote_devices == NULL) {
> + free(tmp);
> remote_devices_capacity = 0;
> remote_devices_cnt = 0;
> return;
Applied, thanks.
--
BR
Szymon Janc
prev parent reply other threads:[~2015-07-29 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 4:20 [PATCH v3] android/client: Fix memory leak while using realloc() Atul Rai
2015-07-29 7:29 ` Szymon Janc [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=32687193.BbdPDPfzcv@leonov \
--to=szymon.janc@tieto.com \
--cc=a.rai@samsung.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sachin.dev@samsung.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