Changes between Version 1 and Version 2 of SponsoringPrograms/GSoC/2021


Ignore:
Timestamp:
Feb 17, 2021, 6:59:05 PM (5 years ago)
Author:
Michael Niedermayer
Comment:

add fuzzing fate projects, they should be flexible timeline wise

Legend:

Unmodified
Added
Removed
Modified
  • SponsoringPrograms/GSoC/2021

    v1 v2  
    7272
    7373
     74== Fuzzing FATE tests in libavformat, libavutil and libswscale ==
     75
     76'''Description:''' FATE is FFmpegs self / regression test system. Fuzzing with oss-fuzz is used to find corner cases which trigger anomalies like undefined behavior. FATE tests are sub optimal to be part of fuzzing as they use hardcoded parameters as input for each test. For example libavutil/tests/des.c runs some random and fixed tests but no tests controlled by some data from a fuzzer. So even if a anomaly occurs during a random test, this would not be reproducible nor could a fuzzer direct execution towards more anomalous cases.
     77
     78'''Expected results:''' Connect most libavformat/tests/*.c libavutil/tests/*.c libswscale/tests/*.c tests to oss-fuzz so that the fuzzer can fully affect the data in each test.
     79
     80'''Prerequisites:''' Good C and Makefile coding skills, basic familiarity with Git, knowledge of oss-fuzz.
     81
     82'''Qualification Task:''' Connect 2 of the 60 FATE tests from libavutil / libavformat / libswscale to work under oss-fuzz, one from libavutil and one from libavformat. Passing qualification will be judged by having working code pushed into FFmpeg git and oss-fuzz git before the deadline given to us for choosing projects.
     83
     84'''Mentor:''' Michael Niedermayer (''michaelni'' in #ffmpeg-devel on Freenode IRC, michaelni@gmx.at)
     85
     86'''Backup Mentor:''' Carl Eugen Hoyos (ceffmpeg [at] gmail [dot] com)
     87
     88
     89== Fuzzing FATE tests in libavcodec, libavfilter and libswresample ==
     90
     91'''Description:''' FATE is FFmpegs self / regression test system. Fuzzing with oss-fuzz is used to find corner cases which trigger anomalies like undefined behavior. FATE tests are sub optimal to be part of fuzzing as they use hardcoded parameters as input for each test. For example libavcodec/tests/snowenc.c runs some random and fixed tests but no tests controlled by some data from a fuzzer. So even if a anomaly occurs during a random test, this would not be reproducible nor could a fuzzer direct execution towards more anomalous cases.
     92
     93'''Expected results:''' Connect most libavcodec/tests/*.c libavfilter/tests/*.c libswresample/tests/*.c src/tests/*.c tools/*.c tests/tools to oss-fuzz so that the fuzzer can fully affect the data in each test/tool.
     94
     95'''Prerequisites:''' Good C and Makefile coding skills, basic familiarity with Git, knowledge of oss-fuzz.
     96
     97'''Qualification Task:''' Connect 2 of the 59 FATE tests and tools from libavcodec / libavfilter / libswresample / src / tools to work under oss-fuzz, one from libavcodec and one from libavfilter. Passing qualification will be judged by having working code pushed into FFmpeg git and oss-fuzz git before the deadline given to us for choosing projects.
     98
     99'''Mentor:''' Michael Niedermayer (''michaelni'' in #ffmpeg-devel on Freenode IRC, michaelni@gmx.at)
     100
     101'''Backup Mentor:''' Carl Eugen Hoyos (ceffmpeg [at] gmail [dot] com)
     102
     103
    74104----
    75105