From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/concatdec: Check recursion depth
Date: Fri, 11 Jul 2025 23:17:33 +0200
Message-ID: <20250711211733.GT29660@pb2> (raw)
In-Reply-To: <aHDLan7drYpW4lrd@phare.normalesup.org>
[-- Attachment #1.1: Type: text/plain, Size: 1355 bytes --]
On Fri, Jul 11, 2025 at 10:29:30AM +0200, Nicolas George wrote:
> Michael Niedermayer (HE12025-07-11):
> > ok, chanegd it to AVERROR_INVALIDDATA
>
> Thanks.
>
> > Yes
> > but this also affects releases, and adding a field to AVFormatContext
> > is an issue for releases as it changes ABI
> >
> > So the concat patch would go into old release branches and the
> > AVFormatContext one into master
> > Unless someone has a better idea ...
>
> What happened to being able to add fields at the end?
a release branch might have a libavformat with version
1.2.3
the next release branch might have a libavformat with version
1.5.2
The problem is if we add a field to 1.2.3 (which would become 1.3.0)
ABI/API requires that field to be in 1.5.2, but it is not
Also besides this problem, 1.3.0 on git masters history likely
added something thats not on the release branches 1.3.0
So, adding at the end is perfectly fine on the linear history
on git master but our release branches, branch off that.
so we would have to hack around things if we really needed to
add a field, we could try to use 1.2.4 or even 1.2.3 with a new field
but this is wrong.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Observe your enemies, for they first find out your faults. -- Antisthenes
[-- 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-07-11 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 10:31 [FFmpeg-devel] [PATCH 1/2] avformat: Add recursion limit Michael Niedermayer
2025-07-07 10:31 ` [FFmpeg-devel] [PATCH 2/2] avformat/concatdec: Check recursion depth Michael Niedermayer
2025-07-07 11:05 ` Nicolas George
2025-07-07 14:58 ` Michael Niedermayer
2025-07-07 15:09 ` Nicolas George
2025-07-07 20:07 ` Michael Niedermayer
2025-07-09 12:04 ` Nicolas George
2025-07-10 23:36 ` Michael Niedermayer
2025-07-11 8:29 ` Nicolas George
2025-07-11 21:17 ` 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=20250711211733.GT29660@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