oss-fuzz/projects/libbpf/project.yaml

homepage: "https://github.com/libbpf/libbpf"
language: c
primary_contact: "andrii.nakryiko@gmail.com"
sanitizers:
  - address
  - undefined
  - memory
auto_ccs:
  - evverx@gmail.com
main_repo: "https://github.com/libbpf/libbpf"
builds_per_day: 4
[libbpf] initial integration (#6608) * [libbpf] initial integration * [libbpf] link against zlib statically it somehow helps to get around https://github.com/google/oss-fuzz/issues/6524 * [libbpf] trim headers * [libbpf] more sanitizers * [libbpf] show the commit libelf is built from to make it easier to roll back to the last known working version should something go wrong * [libbpf] pin libelf to a particular commit to avoid running into unpredictable build failures that can't be controlled by the libbpf project itself. In the future libelf should probably be built using the latest stable release at https://sourceware.org/elfutils/ftp/elfutils-latest.tar.bz2 * [libbpf] add more comment to hoppefully make it easier to make sense of the build script in the foreseeable future * [libbpf] add support for "local" mode without docker to make it easier to build the fuzz target locally: ``` cd projects/libbpf git clone https://github.com/libbpf/libbpf ./build.sh unzip -d CORPUS ./out/bpf-object-fuzzer_seed_corpus.zip ./out/bpf-object-fuzzer CORPUS/ ``` * [libbpf] more comments * [libbpf] add the maintainer's email address * [libbpf] more comments * [libbpf] install libz explicitly * [libbpf] build 4 times a day It should help to prevent OSS-Fuzz from reporting issues that have already been fixed 2021-10-22 04:30:02 +00:00			`homepage: "https://github.com/libbpf/libbpf"`
			`language: c`
			`primary_contact: "andrii.nakryiko@gmail.com"`
			`sanitizers:`
			`- address`
			`- undefined`
			`- memory`
			`auto_ccs:`
			`- evverx@gmail.com`
			`main_repo: "https://github.com/libbpf/libbpf"`
			`builds_per_day: 4`