From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: Sean Young <sean@mess.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH v4l-utils] libdvbv5: leaks and double free in dvb_fe_open_fname()
Date: Fri, 3 May 2019 10:00:36 -0300 [thread overview]
Message-ID: <20190503100036.047693d3@coco.lan> (raw)
In-Reply-To: <20190426154917.75adc64a@coco.lan>
Hi Gregor,
Em Fri, 26 Apr 2019 15:49:17 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> escreveu:
> Em Fri, 26 Apr 2019 18:08:22 +0200
> Gregor Jasny <gjasny@googlemail.com> escreveu:
>
> > Hello,
> >
> > On Fri, 26 Apr 2019, 17:42 Mauro Carvalho Chehab, <
> > mchehab+samsung@kernel.org> wrote:
> >
> > > Gregor,
> > >
> > > This patch messed with all branches since stable-1.12. I applied the revert
> > > patch already on all affected stable branches.
> > >
> > > We should probably release a new fix for them soon.
> > >
> > > Sorry for not looking this earlier.. I got some vacations earlier
> > > this month.
> > >
> >
> > I also got a report in Debian:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927341
Are you planning to release a version 1.16.6 any time soon?
I could likely do it as well, but I would prefer if you can do,
as you know better the drills. We're still receiving new
complaints about this issue at Kaffeine's BZ. Just received
another one today.
Thanks,
Mauro
next prev parent reply other threads:[~2019-05-03 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 16:32 [PATCH v4l-utils] libdvbv5: leaks and double free in dvb_fe_open_fname() Sean Young
2019-04-26 15:13 ` Mauro Carvalho Chehab
2019-04-26 15:42 ` Mauro Carvalho Chehab
[not found] ` <CAJxGH0_bmRiGKCtOf_jFZh_wVsyKR4s1DoDcSvYF7UYx8JNS0g@mail.gmail.com>
2019-04-26 18:49 ` Mauro Carvalho Chehab
2019-05-03 13:00 ` Mauro Carvalho Chehab [this message]
2019-05-03 13:02 ` 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=20190503100036.047693d3@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=gjasny@googlemail.com \
--cc=linux-media@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.