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 <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [h264] Make ff_h264_build_ref_list stricter with AV_EF_EXPLODE
Date: Tue, 12 Aug 2025 11:55:06 +0200
Message-ID: <20250812095506.GG29660@pb2> (raw)
In-Reply-To: <CAPUDrwc8+iAqS6AKBMje8OyKZ5NHZUgehRe9k1t=MyLtFtGQZw@mail.gmail.com>


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

On Thu, Aug 07, 2025 at 02:20:11PM -0700, Dale Curtis wrote:
> On Wed, Aug 6, 2025 at 3:05 PM Michael Niedermayer <michael@niedermayer.cc>
[...]
> 
> >
> >
> > >
> > > Signed-off-by: Dale Curtis <dalecurtis@chromium.org>
> > > ---
> > >  libavcodec/h264_refs.c | 7 +++++++
> > >  1 file changed, 7 insertions(+)
> > >
> > > diff --git a/libavcodec/h264_refs.c b/libavcodec/h264_refs.c
> > > index 74840e5909..e6e3adf502 100644
> > > --- a/libavcodec/h264_refs.c
> > > +++ b/libavcodec/h264_refs.c
> > > @@ -370,6 +370,9 @@ int ff_h264_build_ref_list(H264Context *h,
> > H264SliceContext *sl)
> > >                         i < 0 ? "reference picture missing during
> > reorder\n" :
> > >                                 "mismatching reference\n"
> > >                        );
> > > +                if (h->avctx->err_recognition & AV_EF_EXPLODE) {
> > > +                  return AVERROR_INVALIDDATA;
> > > +                }
> >
> > indention depth is 4 in ffmpeg consistently
> >
> 
> Done.
> 
> 
> >
> >
> > >                  memset(&sl->ref_list[list][index], 0,
> > sizeof(sl->ref_list[0][0])); // FIXME
> > >              } else {
> > >                  for (i = index; i + 1 < sl->ref_count[list]; i++) {
> > > @@ -392,6 +395,10 @@ int ff_h264_build_ref_list(H264Context *h,
> > H264SliceContext *sl)
> > >          for (int index = 0; index < sl->ref_count[list]; index++) {
> > >              if (   !sl->ref_list[list][index].parent
> > >                  || (!FIELD_PICTURE(h) &&
> > (sl->ref_list[list][index].reference&3) != 3)) {
> > > +                if (h->avctx->err_recognition & AV_EF_EXPLODE) {
> > > +                  av_log(h->avctx, AV_LOG_ERROR, "Missing reference
> > picture\n");
> > > +                  return AVERROR_INVALIDDATA;
> > > +                }
> > >                  av_log(h->avctx, AV_LOG_ERROR, "Missing reference
> > picture, default is %d\n", h->default_ref[list].poc);
> >
> > the error out can be after this av_log() avoiding the 2nd av_log() in the
> > if()
> >
> 
> I didn't make this change, but can if you prefer. The existing log implies
> a default is set, but the new log simply indicates the reference picture
> missing is a fatal error.

ok, i will apply this with a commit message not refering to
ff_put_h264_chroma_mc4_ssse3()
AV_EF_EXPLODE is not a fix for a issue with MC

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Opposition brings concord. Out of discord comes the fairest harmony.
-- Heraclitus

[-- 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".

      reply	other threads:[~2025-08-12  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 21:52 Dale Curtis
2025-08-06 22:05 ` Michael Niedermayer
2025-08-07 21:20   ` Dale Curtis
2025-08-12  9:55     ` 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=20250812095506.GG29660@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