From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 3/7] avcodec/bonk: Remove special 32bit case from read_uint_max() Date: Mon, 14 Nov 2022 21:58:24 +0100 Message-ID: <CAPYw7P6VvS307WC0vodJ3oBgyDk8fU5CrMN2ai88ezc0+n=gaw@mail.gmail.com> (raw) In-Reply-To: <20221114203232.GH1814017@pb2> On 11/14/22, Michael Niedermayer <michael@niedermayer.cc> wrote: > On Sun, Nov 06, 2022 at 07:28:48PM +0100, Paul B Mahol wrote: >> On 11/6/22, Michael Niedermayer <michael@niedermayer.cc> wrote: >> > This case seems not to match the reference decoder and it also >> > seems not reachable >> > >> > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> >> > --- >> > libavcodec/bonk.c | 3 +-- >> > 1 file changed, 1 insertion(+), 2 deletions(-) >> > >> > diff --git a/libavcodec/bonk.c b/libavcodec/bonk.c >> > index 04ea4def2f..fca8c246aa 100644 >> > --- a/libavcodec/bonk.c >> > +++ b/libavcodec/bonk.c >> > @@ -136,8 +136,7 @@ static unsigned read_uint_max(BonkContext *s, >> > uint32_t >> > max) >> > if (max == 0) >> > return 0; >> > >> > - if (max >> 31) >> > - return 32; >> > + av_assert0(max >> 31 == 0); >> > >> > for (unsigned i = 1; i <= max - value; i+=i) >> > if (get_bits1(&s->gb)) >> > -- >> > 2.17.1 >> >> >> Not sure, at your risk. >> >> Test lossy mode too. > > piotr provided me with a larger testset including lossy files > they are all unchanged > > will apply this and the other remaining patches. > They look all correct to me, if i am wrong which is always a possibility > iam human ... then you can revert whats wrong of course > Its not for valid, but for fuzzed files. > thx > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > If you drop bombs on a foreign country and kill a hundred thousand > innocent people, expect your government to call the consequence > "unprovoked inhuman terrorist attacks" and use it to justify dropping > more bombs and killing more people. The technology changed, the idea is > old. > _______________________________________________ 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".
next prev parent reply other threads:[~2022-11-14 20:58 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-06 12:34 [FFmpeg-devel] [PATCH 1/7] avcodec/bonk: Use unsigned in predictor_calc_error() to avoid undefined overflows Michael Niedermayer 2022-11-06 12:34 ` [FFmpeg-devel] [PATCH 2/7] avcodec/bonk: Simplify read_uint_max() Michael Niedermayer 2022-11-06 18:30 ` Paul B Mahol 2022-11-10 19:42 ` Michael Niedermayer 2022-11-06 12:34 ` [FFmpeg-devel] [PATCH 3/7] avcodec/bonk: Remove special 32bit case from read_uint_max() Michael Niedermayer 2022-11-06 18:28 ` Paul B Mahol 2022-11-14 20:32 ` Michael Niedermayer 2022-11-14 20:58 ` Paul B Mahol [this message] 2022-11-06 12:34 ` [FFmpeg-devel] [PATCH 4/7] avcodec/bonk: actual_run seems not able to become negative Michael Niedermayer 2022-11-06 18:27 ` Paul B Mahol 2022-11-06 12:34 ` [FFmpeg-devel] [PATCH 5/7] avcodec/bonk: step cannot become 0 without overflowing which is undefined Michael Niedermayer 2022-11-06 18:26 ` Paul B Mahol 2022-11-06 12:34 ` [FFmpeg-devel] [PATCH 6/7] avcodec/bonk: Check step against overflow Michael Niedermayer 2022-11-06 18:25 ` Paul B Mahol 2022-11-10 19:43 ` Michael Niedermayer 2022-11-06 12:34 ` [FFmpeg-devel] [PATCH 7/7] avcodec/bonk: steplet cannot become negative Michael Niedermayer 2022-11-06 18:22 ` Paul B Mahol 2022-11-06 18:31 ` [FFmpeg-devel] [PATCH 1/7] avcodec/bonk: Use unsigned in predictor_calc_error() to avoid undefined overflows Paul B Mahol 2022-11-10 19:41 ` 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='CAPYw7P6VvS307WC0vodJ3oBgyDk8fU5CrMN2ai88ezc0+n=gaw@mail.gmail.com' \ --to=onemda@gmail.com \ --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