[PR] doc/developer.texi: More precisse wording for Robustness (PR #24062)

michaelni via ffmpeg-devel <[email protected]>
Newsgroups gmane.comp.video.ffmpeg.devel
Message-ID <178628960649.59.9564720398291900034@29965ddac10e>
PR #24062 opened by michaelni
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24062
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24062.patch

Fairy took this literally

See: #23985

Signed-off-by: Michael Niedermayer <[email protected]>



>From 01f0a32d54504e6bc68549cbcdf9bc12fa3abf59 Mon Sep 17 00:00:00 2001
From: Michael Niedermayer <[email protected]>
Date: Sun, 9 Aug 2026 17:09:01 +0200
Subject: [PATCH] doc/developer.texi: More precisse wording for Robustness

Fairy takes this literally

See: #23985

Signed-off-by: Michael Niedermayer <[email protected]>
---
 doc/developer.texi | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/doc/developer.texi b/doc/developer.texi
index 0a0cce63f5..92ccedd381 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -411,9 +411,15 @@ The code must behave correctly under such conditions.
 
 @subheading Robustness
 The code must treat as untrusted any bytestream received from a caller or read
-from a file, network, etc. It must not misbehave when arbitrary data is sent to
-it - typically it should print an error message and return
-@code{AVERROR_INVALIDDATA} on encountering invalid input data.
+from a file, network, etc. Arbitrary input must never cause unsafe
+behavior or a security issue.
+
+Common real-world errors of common formats and codecs should be detected where practical,
+reported where appropriate, and handled to produce the best output possible,
+for example through error concealment.
+
+All errors must still be handled safely, but if they are detected,
+reporting or how they are handled is left to the implementation.
 
 @subheading Memory allocation
 The code must use the @code{av_malloc()} family of functions from
-- 
2.52.0

_______________________________________________
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.