Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] STF Idea: Check I/O calls in avformat (robustness)
Date: Mon, 2 Jun 2025 18:08:17 +0100
Message-ID: <f8bef533-3b5f-42d4-80f0-4359faf5433e@gmail.com> (raw)

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.

Cheers,
Grenade Boi

UwU
_______________________________________________
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".

             reply	other threads:[~2025-06-02 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 17:08 Derek Buitenhuis [this message]
2025-06-03 12:05 ` Michael Niedermayer

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=f8bef533-3b5f-42d4-80f0-4359faf5433e@gmail.com \
    --to=derek.buitenhuis@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