From: Johan Hedberg <johan.hedberg@gmail.com>
To: Ludek Finstrle <luf@pzkagis.cz>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC] attrib: Fix memleak if att_data_list_alloc fails
Date: Fri, 19 Oct 2012 10:42:27 +0300 [thread overview]
Message-ID: <20121019074227.GC2243@x220> (raw)
In-Reply-To: <1350549561-16424-1-git-send-email-luf@pzkagis.cz>
Hi Ludek,
On Thu, Oct 18, 2012, Ludek Finstrle wrote:
> Fix for memory leak which was introduced in commit
> f8619bef3406a2134082dc41c208105fe028c09f.
> I tested it with older bluez and rebase for git. Please review it.
> ---
> src/attrib-server.c | 12 +++++++++---
> 1 files changed, 9 insertions(+), 3 deletions(-)
Applied (with the last commit message line removed as suggested by
Vinicius). Thanks.
Johan
prev parent reply other threads:[~2012-10-19 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 12:49 Memory leak introduced in commit f8619bef3406a2134082dc41c208105fe028c09f Ludek Finstrle
2012-10-17 14:03 ` Vinicius Costa Gomes
2012-10-17 14:08 ` Anderson Lizardo
2012-10-18 8:39 ` [RFC] attrib: Fix memleak if att_data_list_alloc fails Ludek Finstrle
2012-10-18 23:20 ` Vinicius Costa Gomes
2012-10-19 7:42 ` Johan Hedberg [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=20121019074227.GC2243@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luf@pzkagis.cz \
/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).