From: Nuo Mi <nuomi2021@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] vvcdec: Mark as experimental Date: Sat, 16 Mar 2024 22:50:32 +0800 Message-ID: <CAFXK13c-Mp_fkrz6mgu1-sm_4torbrf9TCeLK=YuUgi3tytbcg@mail.gmail.com> (raw) In-Reply-To: <AS8P250MB074442058336C25CBB286FA58F282@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> On Fri, Mar 15, 2024 at 11:05 PM Andreas Rheinhardt < andreas.rheinhardt@outlook.com> wrote: > Frank Plowman: > > On 15/03/2024 10:22, Kieran Kunhya wrote: > >> On Thu, 14 Mar 2024, 22:54 Michael Niedermayer, <michael@niedermayer.cc > > > >> wrote: > >> > >>> On Wed, Feb 07, 2024 at 10:55:18PM +0000, Kieran Kunhya wrote: > >>>> On Wed, 7 Feb 2024 at 22:06, Paul B Mahol <onemda@gmail.com> wrote: > >>>> > >>>>> On Wed, Feb 7, 2024 at 10:13 PM Kieran Kunhya <kierank@obe.tv> > wrote: > >>>>> > >>>>>> $subj > >>>>>> > >>>>>> As discussed at FOSDEM. > >>>>>> > >>>>> > >>>>> Author of this patch above is forced to FUZZ this decoder until > >>>>> experimental flag is removed. > >>>>> > >>>> > >>>> Sure, I will set some fuzzers up over the weekend. > >>> > >>> over a month later ... > >>> has this been done ? > >>> > >>> > >>> thx > >>> > >>> [...] > >>> > >> > >> Frank said there was no need as he was doing it himself. > >> > >> I do not appreciate your passive aggressive tone. > >> > >> Kieran > >> > > > > I have been fuzzing since the end of January. Various patches have made > > the decoder much more robust than it was then. Still getting a crash on > > occasion, but most are now false positives due to assertion failures > > rather than segmentation faults or other potential security issues. > > That being said, the hardware I am using is extremely modest compared to > > oss-fuzz's. > > An assertion failure is not a false positive. Even if it is an av_assert2. > Agree, we need to return PATCH_WELCOME for them too. > > - Andreas > > _______________________________________________ > 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".
next prev parent reply other threads:[~2024-03-16 14:50 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-07 21:13 Kieran Kunhya 2024-02-07 22:06 ` Paul B Mahol 2024-02-07 22:55 ` Kieran Kunhya 2024-02-08 6:00 ` Nuo Mi 2024-02-08 18:16 ` Kieran Kunhya 2024-02-09 3:54 ` Nuo Mi 2024-02-13 2:56 ` Nuo Mi 2024-02-14 2:57 ` Nuo Mi 2024-02-14 9:41 ` Kieran Kunhya 2024-03-14 22:54 ` Michael Niedermayer 2024-03-15 10:22 ` Kieran Kunhya 2024-03-15 15:00 ` Frank Plowman 2024-03-15 15:04 ` Andreas Rheinhardt 2024-03-16 14:50 ` Nuo Mi [this message] 2024-03-16 14:49 ` Nuo Mi 2024-02-14 11:49 ` Andreas Rheinhardt 2024-02-14 13:41 ` Kieran Kunhya 2024-03-13 21:34 ` James Almer
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='CAFXK13c-Mp_fkrz6mgu1-sm_4torbrf9TCeLK=YuUgi3tytbcg@mail.gmail.com' \ --to=nuomi2021@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