From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/avcodec: don't uninitialize ch_layout in avcodec_close()
Date: Sun, 20 Mar 2022 19:12:43 -0300
Message-ID: <6995d99f-73e4-0a00-ee74-5feb194b093f@gmail.com> (raw)
In-Reply-To: <CA+anqdyeawwrSkAabBDmE3XVQ0O-TZkEs0UpxB0=2qPCfXZv7g@mail.gmail.com>
On 3/20/2022 7:01 PM, Hendrik Leppkes wrote:
> On Sun, Mar 20, 2022 at 7:52 PM James Almer <jamrial@gmail.com> wrote:
>>
>> On 3/19/2022 4:50 AM, Hendrik Leppkes wrote:
>>> On Sat, Mar 19, 2022 at 4:04 AM James Almer <jamrial@gmail.com> wrote:
>>>>
>>>> The function is not meant to clear codec parameters, and the lavf demux code
>>>> relies on this behavior.
>>>> Regression since 327efa66331ebdc0087c6b656059a8df2f404019.
>>>>
>>>> Signed-off-by: James Almer <jamrial@gmail.com>
>>>> ---
>>>> libavcodec/avcodec.c | 6 ++++++
>>>> 1 file changed, 6 insertions(+)
>>>>
>>>> diff --git a/libavcodec/avcodec.c b/libavcodec/avcodec.c
>>>> index 38bdaad4fa..253c9f56cc 100644
>>>> --- a/libavcodec/avcodec.c
>>>> +++ b/libavcodec/avcodec.c
>>>> @@ -469,6 +469,7 @@ void avsubtitle_free(AVSubtitle *sub)
>>>>
>>>> av_cold int avcodec_close(AVCodecContext *avctx)
>>>> {
>>>> + AVChannelLayout ch_layout;
>>>> int i;
>>>>
>>>> if (!avctx)
>>>> @@ -524,7 +525,12 @@ av_cold int avcodec_close(AVCodecContext *avctx)
>>>>
>>>> if (avctx->priv_data && avctx->codec && avctx->codec->priv_class)
>>>> av_opt_free(avctx->priv_data);
>>>> + /* av_opt_free() will uninitialize avctx->ch_layout, but we want to keep it.
>>>> + It will be uninitialized in avcodec_free_context() */
>>>> + ch_layout = avctx->ch_layout;
>>>> + memset(&avctx->ch_layout, 0, sizeof(avctx->ch_layout));
>>>> av_opt_free(avctx);
>>>> + avctx->ch_layout = ch_layout;
>>>> av_freep(&avctx->priv_data);
>>>> if (av_codec_is_encoder(avctx->codec)) {
>>>> av_freep(&avctx->extradata);
>>>
>>> This feels pretty ugly and still a bit risky that any call to
>>> av_opt_free could invalidate data its not supposed to. Maybe we should
>>> have a flag for AVOptions instead where av_opt_free won't touch an
>>> entry, because its only there to set/get it, not manage its memory?
>>
>> Where would that flag be set? av_opt_free() takes none. And that
>> function exists purely to free strings, dictionaries, and now
>> uninitialize AVChannelLayout elements in a struct. If you don't want to
>> free what av_opt_set() allocated, you shouldn't call av_opt_free() at all.
>>
>
> On the AVOption element in the table, with the other AV_OPT_FLAG_*
Oh, you meant flagging the actual AVOption. My bad, i for some reason
thought you meant having the user flag which options they wanted to "own".
I'll try to implement this. Any suggestion for the flag name?
AV_OPT_FLAG_NO_FREE?
> _______________________________________________
> 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".
_______________________________________________
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".
next prev parent reply other threads:[~2022-03-20 22:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 3:04 James Almer
2022-03-19 7:50 ` Hendrik Leppkes
2022-03-20 18:51 ` James Almer
2022-03-20 22:01 ` Hendrik Leppkes
2022-03-20 22:12 ` James Almer [this message]
2022-03-20 22:34 ` Marton Balint
2022-03-20 22:52 ` James Almer
2022-03-20 23:09 ` Marton Balint
2022-03-19 13:47 ` Anton Khirnov
2022-03-20 17:03 ` James Almer
2022-03-20 19:06 ` James Almer
2022-03-20 23:38 ` Andreas Rheinhardt
2022-03-21 7:37 ` Hendrik Leppkes
2022-03-21 7:51 ` Anton Khirnov
2022-03-21 12:10 ` James Almer
2022-03-21 21:08 ` Andreas Rheinhardt
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=6995d99f-73e4-0a00-ee74-5feb194b093f@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