From: Kacper Michajlow <kasper93@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] tools/target_enc_fuzzer: Add slices and level for FFv1 Date: Mon, 12 Aug 2024 02:33:57 +0200 Message-ID: <CABPLASS+5QfNVWgw779xJo7ZJG+OvPB0F1ezgqaQ1YNfds72Gw@mail.gmail.com> (raw) In-Reply-To: <CABPLASQD1EP_uLkpAXK9oA6xwFwsQHhE3aOX_u_eraySWgW6YQ@mail.gmail.com> On Mon, 12 Aug 2024 at 02:06, Kacper Michajlow <kasper93@gmail.com> wrote: > > On Sun, 11 Aug 2024 at 10:59, Michael Niedermayer > <michael@niedermayer.cc> wrote: > > > > Sponsored-by: Sovereign Tech Fund > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > > --- > > tools/target_enc_fuzzer.c | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/tools/target_enc_fuzzer.c b/tools/target_enc_fuzzer.c > > index 059d7830710..59c2db4bb42 100644 > > --- a/tools/target_enc_fuzzer.c > > +++ b/tools/target_enc_fuzzer.c > > @@ -149,6 +149,8 @@ int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) { > > av_dict_set_int(&opts, "coder", coder, 0); > > av_dict_set_int(&opts, "context", bytestream2_get_byte(&gbc)&1, 0); > > av_dict_set_int(&opts, "slicecrc", bytestream2_get_byte(&gbc)&1, 0); > > + ctx->slices = bytestream2_get_byte(&gbc); > > + ctx->level = bytestream2_get_byte(&gbc) % 6 - 1; > > Note sure that's correct. Depending on the codec numeric level value > may differ, but generally it has higher value. Like 62 for "6.2" in > h264 case, or 186 for "6.2" for h265 case. I would just remove `% 6 - > 1` and let fuzzer find interesting values for each codec. Oh, sorry. From the diff I couldn't see that it is in `case AV_CODEC_ID_FFV1`, so my remark is invalid. Still might be useful to also test invalid `level` values. > - Kacper > > > break;} > > } > > } > > -- > > 2.45.2 > > > > _______________________________________________ > > 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". _______________________________________________ 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:[~2024-08-12 0:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-08-11 8:59 Michael Niedermayer 2024-08-12 0:06 ` Kacper Michajlow 2024-08-12 0:33 ` Kacper Michajlow [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=CABPLASS+5QfNVWgw779xJo7ZJG+OvPB0F1ezgqaQ1YNfds72Gw@mail.gmail.com \ --to=kasper93@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