From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] avcodec/hcadec: support decoding with extradata provided in first packet
Date: Wed, 4 Oct 2023 15:35:02 -0300
Message-ID: <15f97a92-8bfc-4324-83e1-7ffd74f94482@gmail.com> (raw)
In-Reply-To: <20231004172254.GJ3543730@pb2>
On 10/4/2023 2:22 PM, Michael Niedermayer wrote:
> On Mon, Oct 02, 2023 at 10:56:20PM -0300, James Almer wrote:
>> On 10/2/2023 7:23 PM, Michael Niedermayer wrote:
>>> Hi
>>>
>>> On Tue, Sep 05, 2023 at 09:25:45PM +0000, Paul B Mahol wrote:
>>>> ffmpeg | branch: master | Paul B Mahol <onemda@gmail.com> | Tue Sep 5 23:14:58 2023 +0200| [d464a687c9dd03246795d62151809167e8381932] | committer: Paul B Mahol
>>>>
>>>> avcodec/hcadec: support decoding with extradata provided in first packet
>>>
>>> I cannot find this patch on the mailing list
>>>
>>> Also this adds null pointer writes
>>> The init_hca() function which previously was only called once and failure
>>> ended all further processing now is called optionally per frame and its
>>> failure does not stop further processing so half initialized contexts
>>> can be created by an attacker
>>>
>>> Note, this sort of stuff delays the release
>>>
>>> thx
>>
>> Does the following fix it?
>
> the testcase no longer crashes with this
>
> thx
Will apply it.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2023-10-04 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230905212547.00596410A28@natalya.videolan.org>
2023-10-02 22:23 ` Michael Niedermayer
2023-10-03 1:56 ` James Almer
2023-10-04 17:22 ` Michael Niedermayer
2023-10-04 18:35 ` James Almer [this message]
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=15f97a92-8bfc-4324-83e1-7ffd74f94482@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git