public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Sean Young <sean@mess.org>
Cc: Gregor Jasny <gjasny@googlemail.com>,
	CHEMLA Samuel <chemla.samuel@gmail.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@s-opensource.com>
Subject: Re: [Bug report] dvbv5-zap crash dvb-tool ARMHF builds
Date: Thu, 21 Mar 2019 08:30:44 -0300	[thread overview]
Message-ID: <20190321083044.621f1922@coco.lan> (raw)
In-Reply-To: <20190321094127.ysurm4u26zugmnmv@gofer.mess.org>

Em Thu, 21 Mar 2019 09:41:28 +0000
Sean Young <sean@mess.org> escreveu:

> On Wed, Mar 20, 2019 at 08:38:52PM +0100, Gregor Jasny wrote:
> > Hello Mauro,
> > 
> > On 19.03.19 20:45, Mauro Carvalho Chehab wrote:
> > > Hi Gregor,
> > > 
> > > Samuel reported in priv that the issues he had with user after free were
> > > solved by the patchsets merged at 1.12 and 1.16 stable branches.
> > > 
> > > Could you please generate a new staging release for them?
> > 
> > Sure, I can create a new 1.12 and 1.16 stable release. But when reviewing
> > the patches for approval by debian release managers I noticed an additional
> > double-free that Sean addressed with the following patch:
> > 
> > > https://git.linuxtv.org/v4l-utils.git/commit/?id=ebd890019ba7383b8b486d829f6683c8f49fdbda
> > 
> > Could you please give that patch a thorough review, some testing, and
> > cherry-pick it to stable-1.12 and -1.16 as well?
> 
> I did test it myself (and also under valgrind). The bad paths are hard
> to hit though. I'd say just go ahead with merging and releasing, the patch
> isn't that controversial (I hope!).

I went ahead and cherry-picked the relevant patches to -1.12, -1.14 and
-1.16, and tested both dvbv5-zap and dvbv5-scan with all versions. So, we can
release a new minor version for all those stable branches.

After the patches, on my tests, I didn't get any memory leaks or
double-free issues.

It should be noticed that I had to add a new patch at -1.14, due to
the usage of minor() and major() macros, as one of the files there
were not including sys/sysmacros.h. Without that, I was getting
compilation errors.

Funny enough, this header was already included on two other places
within -1.14.

As the major() and minor() macros were added at glibc 2.3.3[1], released
in 2004 [2], it should be save to include sys/sysmacros.h
unconditionally at stable-1.14.

[1] according with "man 3 makedev", as pointed by:
https://stackoverflow.com/questions/22240973/major-and-minor-macros-defined-in-sys-sysmacros-h-pulled-in-by-iterator

[2] https://ftp.gnu.org/gnu/libc/'s glibc tarball is from 2004-08-03.

Thanks,
Mauro

  reply	other threads:[~2019-03-21 11:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f4b69417-06c3-f9ab-2973-ae23d76088b8@gmail.com>
     [not found] ` <29bad771-843c-1dee-906c-6e9475aed7d8@gmail.com>
2019-03-12 15:07   ` [Bug report] dvbv5-zap crash dvb-tool ARMHF builds Gregor Jasny
2019-03-15 22:34     ` Sean Young
2019-03-17  9:52       ` Mauro Carvalho Chehab
2019-03-19 19:45         ` Mauro Carvalho Chehab
2019-03-20 19:38           ` Gregor Jasny
2019-03-21  9:41             ` Sean Young
2019-03-21 11:30               ` Mauro Carvalho Chehab [this message]
2019-03-21 19:59                 ` Gregor Jasny
     [not found]                   ` <CANJnhGfRtEwAony5Z4rFMPcu58aF2k0G+9NSkMKsq_PhfmSNqw@mail.gmail.com>
2019-03-25 17:08                     ` Mauro Carvalho Chehab
2019-03-26  7:35                       ` Samuel CHEMLA
2019-03-26 13:26                         ` Sean Young
2019-03-26 15:10                           ` Samuel CHEMLA
2019-03-26 15:31                             ` Mauro Carvalho Chehab
2019-03-28 18:48                               ` Samuel CHEMLA
2019-03-28 19:17                                 ` Mauro Carvalho Chehab
2019-03-28 19:48                                   ` Gregor Jasny
2019-03-28 20:04                                     ` Mauro Carvalho Chehab
2019-04-01 18:58                                   ` Samuel CHEMLA
2019-04-08  6:32                                     ` Samuel CHEMLA

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=20190321083044.621f1922@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=chemla.samuel@gmail.com \
    --cc=gjasny@googlemail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=sean@mess.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