Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [PATCH] avcodec/tiff: Check order only for tags that we process
Date: Tue, 11 Nov 2025 16:27:49 +0100
Message-ID: <aRNV9TwhamAPtFL_@neo> (raw)
In-Reply-To: <20251105112952.1474387-2-mail@mathias.im>


[-- Attachment #1.1: Type: text/plain, Size: 1230 bytes --]

Hi Mathias

On Wed, Nov 05, 2025 at 12:29:53PM +0100, Mathias Koehler via ffmpeg-devel wrote:
> The initial out of order check was introduced with commit
> ad29f9e47cb avcodec/tiff: Restrict tag order based on specification
> 
> This changes the check to only check against tags the we process
> since tags that we don't process shouldn't cause any bugs.
> 
> Example of CinemaDNG files with incorrect ordered tags
> that causes problems: https://www.dji.com/de/inspire-3/samples
> ---
>  libavcodec/tiff.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)

what tags are that ?
any "user" tags that can be more cleanly excluded ?

I dont like this patch because its not really leading itself to a
clean implementation when more exceptions appear

I think its better to define in a clean, terse and general way the ordering
our decoder can handle. Something that works with all tags not just ones we
skip

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The real ebay dictionary, page 2
"100% positive feedback" - "All either got their money back or didnt complain"
"Best seller ever, very honest" - "Seller refunded buyer after failed scam"

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

      reply	other threads:[~2025-11-11 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 11:29 [FFmpeg-devel] " Mathias Koehler via ffmpeg-devel
2025-11-11 15:27 ` Michael Niedermayer via ffmpeg-devel [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=aRNV9TwhamAPtFL_@neo \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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