public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: libdvbv5: dvb_table_pat_init is leaking memory
Date: Thu, 28 Nov 2013 10:24:10 -0200	[thread overview]
Message-ID: <20131128102410.45bbe3a2@samsung.com> (raw)
In-Reply-To: <20131127204642.05ddaac5@samsung.com>

Hi Gregor,

Em Wed, 27 Nov 2013 20:46:42 -0200
Mauro Carvalho Chehab <m.chehab@samsung.com> escreveu:

> Em Wed, 27 Nov 2013 20:31:21 -0200
> Mauro Carvalho Chehab <mchehab@infradead.org> escreveu:
> 
> > Hi Gregor,
> > 
> > Em Wed, 27 Nov 2013 22:55:32 +0100
> > Gregor Jasny <gjasny@googlemail.com> escreveu:
> > 
> > > Hello,
> > > 
> > > Coverity noticed that dvb_table_pat_init leaks the reallocated memory
> > > stored in pat:
> > > http://git.linuxtv.org/v4l-utils.git/blob/HEAD:/lib/libdvbv5/descriptors/pat.c#l26
> > > 
> > > Mauro, could you please check?
> > 
> > On my tests with Valgrind, I'm not noticing any memory leak there, at
> > least on the very latest version I pushed today[1].

After a good resting night, I reviewed it, and it turns that memory leaks
can occur.

So, I re-worked the logic. I also fixed the other bugs pointed by Coverity
today. Could you please re-run the Coverity tests, to see if everything is
OK with the current version?

Thanks!
Mauro


  reply	other threads:[~2013-11-28 12:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJxGH09uZhZ0m4GcpAF4moURp18hPmBh5cOP_ZHoNxAaadL_XQ@mail.gmail.com>
2013-11-27 22:31 ` libdvbv5: dvb_table_pat_init is leaking memory Mauro Carvalho Chehab
2013-11-27 22:46   ` Mauro Carvalho Chehab
2013-11-28 12:24     ` Mauro Carvalho Chehab [this message]
2013-12-15 18:03       ` Gregor Jasny

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=20131128102410.45bbe3a2@samsung.com \
    --to=m.chehab@samsung.com \
    --cc=gjasny@googlemail.com \
    --cc=linux-media@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