From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: Sean Young <sean@mess.org>,
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: Tue, 19 Mar 2019 16:45:16 -0300 [thread overview]
Message-ID: <20190319164507.7f95af89@coco.lan> (raw)
In-Reply-To: <20190317065242.137cb095@coco.lan>
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?
Thanks!
Mauro
Em Sun, 17 Mar 2019 06:52:42 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> escreveu:
> Em Fri, 15 Mar 2019 22:34:25 +0000
> Sean Young <sean@mess.org> escreveu:
>
> > Hi,
> >
> > On Tue, Mar 12, 2019 at 04:07:23PM +0100, Gregor Jasny wrote:
> > > Hello Mauro,
> > >
> > > below you find a bug report about an use-after-free in dvbv5-zap.
> > >
> > > On 12.03.19 13:37, CHEMLA Samuel wrote:
> > > > please find a bug report that seems to concern ARMHF builds of dvbv5-zap
> > > > (dvb-tool package) : https://bugs.launchpad.net/raspbian/+bug/1819650
> > > > I filed it against raspbian because I thought it was a raspbian problem,
> > > > but don't think they re-build their own package, but use debian ones
> > > > instead...
> > >
> >
> > So I can reproduce the issue with v4l-utils 1.12.3 but not with current
> > v4l-utils (or dvbv5-zap). It looks exactly like the issue fixed in
> > commit 6e21f6f34c1d7c3a7a059062e1ddd9705c984e2c (but I did not cherry-pick
> > and test that on top of 1.12.3 to test that theory).
>
> I added it to stable/1.12 and another patch fixing the initialization of
> the parameters struct, with Samuel reported to fix the issue upstream
> (He pinged me in priv too, and I'm helping him to track it).
>
> Samuel,
>
> Could you please check if the 1.12 stable branch is OK now?
>
> Regards,
> Mauro
> Thanks,
> Mauro
Thanks,
Mauro
next prev parent reply other threads:[~2019-03-19 19:45 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 [this message]
2019-03-20 19:38 ` Gregor Jasny
2019-03-21 9:41 ` Sean Young
2019-03-21 11:30 ` Mauro Carvalho Chehab
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=20190319164507.7f95af89@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