From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avformat/demux: use io_close2 when closing avfromat
Date: Sat, 31 May 2025 00:08:10 +0200
Message-ID: <20250530220810.GP29660@pb2> (raw)
In-Reply-To: <AS8P250MB07443261EC3F1645B55907A88F61A@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>
[-- Attachment #1.1: Type: text/plain, Size: 2588 bytes --]
On Fri, May 30, 2025 at 10:48:29PM +0200, Andreas Rheinhardt wrote:
> Michael Niedermayer:
> > On Sat, May 17, 2025 at 03:03:19PM +0200, Andreas Rheinhardt wrote:
> >> Andreas Rheinhardt:
> >>> Kacper Michajłow:
> >>>> It's not valid to call avio_close() on context that has not been open
> >>>> with avio_open().
> >>>>
> >>>> This fixes use of custom IO. (io_open / io_close2 callbacks)
> >>>>
> >>>> Note that by default io_close2 is set to io_close2_default() which calls
> >>>> avio_close(), so default case will work the same as before.
> >>>>
> >>>> Signed-off-by: Kacper Michajłow <kasper93@gmail.com>
> >>>> ---
> >>>> libavformat/demux.c | 3 +--
> >>>> 1 file changed, 1 insertion(+), 2 deletions(-)
> >>>>
> >>>> diff --git a/libavformat/demux.c b/libavformat/demux.c
> >>>> index 2795863567..ecd4f40da9 100644
> >>>> --- a/libavformat/demux.c
> >>>> +++ b/libavformat/demux.c
> >>>> @@ -383,11 +383,10 @@ void avformat_close_input(AVFormatContext **ps)
> >>>> if (ffifmt(s->iformat)->read_close)
> >>>> ffifmt(s->iformat)->read_close(s);
> >>>>
> >>>> + ff_format_io_close(s, &pb);
> >>>> avformat_free_context(s);
> >>>>
> >>>> *ps = NULL;
> >>>> -
> >>>> - avio_close(pb);
> >>>> }
> >>>>
> >>>> static void force_codec_ids(AVFormatContext *s, AVStream *st)
> >>>
> >>> avformat_open_input() sets AVFMT_FLAG_CUSTOM_IO when using custom IO and
> >>> avformat_close_input() checks for this and does not free the
> >>> AVFormatContext's AVIOContext in this case (but does avio_close(NULL) in
> >>> this case).
> >>> Your patch furthermore presumes that the custom IO context is compatible
> >>> with io_close2, which need not be true at all (one can use custom IO
> >>> without ever touching io_open/io_close2 pointers; I expect users that
> >>> use custom IO, but not formats that open new AVIOContexts to do so).
> >>
> >> On reading a bit further, init_input() uses io_open to open the
> >> AVIOContext in case no AVIOContext was supplied (and one is needed).
> >> This means that the AVFMT_FLAG_CUSTOM_IO flag is misleading, as it is
> >> possible to use custom IO even with this flag unset.
> >
> >> It also means that
> >> your patch is likely correct.
> >
> > does any reason remain against applying it ?
> >
>
> I don't see any.
ok, will apply it then
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
What is kyc? Its a tool that makes you give out your real ID, while criminals
give out a forged ID card.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2025-05-30 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 3:50 Kacper Michajłow
2025-05-17 3:50 ` [FFmpeg-devel] [PATCH 2/2] avformat/imfdec: inherit opaque from parent AVFormatContext Kacper Michajłow
2025-05-17 4:15 ` Pierre-Anthony Lemieux
2025-05-22 22:58 ` Michael Niedermayer
2025-05-17 12:39 ` [FFmpeg-devel] [PATCH 1/2] avformat/demux: use io_close2 when closing avfromat Andreas Rheinhardt
2025-05-17 13:03 ` Andreas Rheinhardt
2025-05-17 18:59 ` Kacper Michajlow
2025-05-30 19:47 ` Michael Niedermayer
2025-05-30 20:48 ` Andreas Rheinhardt
2025-05-30 22:08 ` Michael Niedermayer [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=20250530220810.GP29660@pb2 \
--to=michael@niedermayer.cc \
--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