From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] STF Idea: Check I/O calls in avformat (robustness)
Date: Tue, 3 Jun 2025 14:05:09 +0200
Message-ID: <20250603120509.GK29660@pb2> (raw)
In-Reply-To: <f8bef533-3b5f-42d4-80f0-4359faf5433e@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1395 bytes --]
Hi Derek
On Mon, Jun 02, 2025 at 06:08:17PM +0100, Derek Buitenhuis wrote:
> Hi,
>
> Dropping this grenade in here then unsubscribing.
>
> I see a lot of discussion on FEC, protocols, etc. for STF.
>
> But having those is almost pointless given avformat doesn't even check
> read and write calls in most places (even ignoring ensured seekbacks,
> buffer, etc.).
>
> A quick grep shows ~462 unchecked avio_r*, for example.
>
> What this means is that avformat itself is basically ununsuable in
> anything but perfect network conditions.
>
> Given STF is supposed to be used for useful stability and maitenence
> work, I propose a project to properly check I/O in avformat, so that
> any hiccup doesn't explode everything in unexpected ways.
>
> This exactly the sort of slog (boring, tedious, but extremely useful)
> that requires someone being paid to do to get done.
I think this is a great idea
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Modern terrorism, a quick summary: Need oil, start war with country that
has oil, kill hundread thousand in war. Let country fall into chaos,
be surprised about raise of fundamantalists. Drop more bombs, kill more
people, be surprised about them taking revenge and drop even more bombs
and strip your own citizens of their rights and freedoms. to be continued
[-- 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-06-03 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 17:08 Derek Buitenhuis
2025-06-03 12:05 ` 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=20250603120509.GK29660@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