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] [PATCH 2/2] avcodec/sanm: avoid using k in left pxoff check
Date: Sat, 31 May 2025 00:51:30 +0200
Message-ID: <20250530225130.GQ29660@pb2> (raw)
In-Reply-To: <CAOLZvyF63K=N6FNqXN+TJQpiYAnoX23=E6cHebgPEE_m2H-c9g@mail.gmail.com>


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

Hi Manuel

On Fri, May 30, 2025 at 10:54:01PM +0200, Manuel Lauss wrote:
> Hi Michael,
> 
> On Fri, May 30, 2025 at 9:52 PM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> >
> > Hi Manual
> >
> > On Wed, May 14, 2025 at 03:39:53AM +0200, Michael Niedermayer wrote:
> > > k is always 4 here and it seems this is not what was intended
> > > replacing it with 0 works but it may be wrong
> > >
> > > This needs review
> > >
> > > Fixes: out of array read
> > > Fixes: 409593384/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_SANM_fuzzer-6488251907244032
> > >
> > > Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
> > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> > > ---
> > >  libavcodec/sanm.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > please review, this patch is just written based on gut feeling,
> > its just clear that the code before was buggy
> 
> > >
> > > diff --git a/libavcodec/sanm.c b/libavcodec/sanm.c
> > > index 00bfef00fe8..ec429e1a002 100644
> > > --- a/libavcodec/sanm.c
> > > +++ b/libavcodec/sanm.c
> > > @@ -734,7 +734,7 @@ static int old_codec4(SANMVideoContext *ctx, GetByteContext *gb, int top, int le
> > >              }
> > >
> > >              /* smooth top and left block borders with neighbours */
> > > -            if (((pxoff - p + k) < 0) || ((pxoff - p + k) >= maxpxo)
> > > +            if (((pxoff - p + 0) < 0) || ((pxoff - p + k) >= maxpxo)
> > >                  || ((pxoff + 3 * p) < 0) || ((pxoff + 3 * p) >= maxpxo)
> > >                  || (i == 0) || (j == 0))
> > >                  continue;
> 
> Oops, yes, that change is correct.

will apply


> I think you should just rip the whole block-smoothing block out
> entirely: it creates a "sawtooth" pattern
> which is more annoying than the "blockiness" it tries to soften.

probably, but i just wanted to fix the out of array access,
ill leave improvment beyond that to others

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Rewriting code that is poorly written but fully understood is good.
Rewriting code that one doesnt understand is a sign that one is less smart
than the original author, trying to rewrite it will not make it better.

[-- 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-05-30 22:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14  1:39 [FFmpeg-devel] [PATCH 1/2] avcodec/ffv1enc_template: Fix remaining space check Michael Niedermayer
2025-05-14  1:39 ` [FFmpeg-devel] [PATCH 2/2] avcodec/sanm: avoid using k in left pxoff check Michael Niedermayer
2025-05-30 19:52   ` Michael Niedermayer
2025-05-30 20:54     ` Manuel Lauss
2025-05-30 22:51       ` Michael Niedermayer [this message]
2025-06-03 10:30         ` Manuel Lauss
2025-06-04 11:00           ` Michael Niedermayer
2025-06-04 20:06             ` Manuel Lauss
2025-06-04 23:21               ` Michael Niedermayer
2025-05-30 19:49 ` [FFmpeg-devel] [PATCH 1/2] avcodec/ffv1enc_template: Fix remaining space check 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=20250530225130.GQ29660@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