public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-bluetooth@vger.kernel.org, Tedd Ho-Jeong An <hj.tedd.an@gmail.com>
Subject: Re: [Bluez PATCH ] Fix memory leaks in obex
Date: Mon, 17 May 2021 13:17:32 -0400	[thread overview]
Message-ID: <11751357.O9o76ZdvQC@x2> (raw)
In-Reply-To: <9af2be8769f9b8b1146424a72735084984fde825.camel@gmail.com>

On Monday, May 17, 2021 1:10:58 PM EDT Tedd Ho-Jeong An wrote:
> On Sat, 2021-05-15 at 09:43 -0400, Steve Grubb wrote:
> > This patch fixes a couple memory leaks.
> > 
> > In filesystem, g_file_get_contents allocates fresh memory to buf.
> > It needs to be freed after conversion to a GString object.
> > 
> > Destination was missed on an error path as is mld.
> > 
> > ---
> > obexd/plugins/filesystem.c     | 2 +-
> > obexd/plugins/ftp.c            | 8 ++++++--
> > obexd/plugins/messages-dummy.c | 1 +
> > 3 files changed, 8 insertions(+), 3 deletions(-)
> > 
> > diff --git a/obexd/plugins/filesystem.c b/obexd/plugins/filesystem.c
> > index 09bff8ad0..44e3cf3d2 100644
> > --- a/obexd/plugins/filesystem.c
> > +++ b/obexd/plugins/filesystem.c@@ -416,6 +416,7 @@ static void
> > *capability_open(const char *name, int oflag, mode_t mode,
>
> CI wasn't able to apply the patch and couldn't run the tests, and I think
> because of this line.

Hmm. Apologies. I'll regenerate the patch and send it again.

Cheers,
-Steve



  reply	other threads:[~2021-05-17 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 13:43 [Bluez PATCH ] Fix memory leaks in obex Steve Grubb
2021-05-17 17:10 ` Tedd Ho-Jeong An
2021-05-17 17:17   ` Steve Grubb [this message]
2021-05-19 18:09 ` Luiz Augusto von Dentz

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=11751357.O9o76ZdvQC@x2 \
    --to=sgrubb@redhat.com \
    --cc=hj.tedd.an@gmail.com \
    --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