| Files | Last commit | Last update |
|---|---|---|
[Fuzzing] move fuzz test in main repo add more fuzz test (#2420) Signed-off-by: Arjun Singh <ajsinghyadav00@gmail.com> | 2 years ago | |
[Fuzzing] move fuzz test in main repo add more fuzz test (#2420) Signed-off-by: Arjun Singh <ajsinghyadav00@gmail.com> | 2 years ago | |
[Fuzzing] move fuzz test in main repo add more fuzz test (#2420) Signed-off-by: Arjun Singh <ajsinghyadav00@gmail.com> | 2 years ago | |
[Fuzzing] move fuzz test in main repo add more fuzz test (#2420) Signed-off-by: Arjun Singh <ajsinghyadav00@gmail.com> | 2 years ago | |
[Fuzzing] move fuzz test in main repo add more fuzz test (#2420) Signed-off-by: Arjun Singh <ajsinghyadav00@gmail.com> | 2 years ago | |
[Fuzzing] move fuzz test in main repo add more fuzz test (#2420) Signed-off-by: Arjun Singh <ajsinghyadav00@gmail.com> | 2 years ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
Refactor NULL with nullptr in test (#3464) | 2 months ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
fix(fuzzing): return 0 (not 1) from the size guard in every harness (#3579) LLVMFuzzerTestOneInput may only return 0 (input consumed) or -1 (input rejected); libFuzzer asserts this after every call (compiler-rt/lib/fuzzer/FuzzerLoop.cpp:622) and runs the empty input first, so every harness here aborts an assert-enabled libFuzzer at startup. Returning 0 keeps out-of-range inputs out of the corpus (the harness body is still skipped) and matches the convention newer harnesses already use. All 18 test/fuzzing/fuzz_*.cpp harnesses share the same guard. Signed-off-by: li-lizhe <147392333@qq.com> | 1 month ago | |
Extend fuzz harness suite and fix false positive Extends the fuzzing suite to a broader set of targets. The main goal here is to improve code coverage, of which a recent report is available here: https://storage.googleapis.com/oss-fuzz-coverage/brpc/reports/20260326/linux/src/report.html This also fixes false positives in some of the fuzzing harnesses due to a missing Socket. This fixes issues e.g. https://issues.oss-fuzz.com/issues/42532345 The new fuzzing harnesses and the fix should show meaningful coverage gains. Signed-off-by: David Korczynski <david@adalogics.com> | 7 months ago |
| Files | Last commit | Last update |
|---|---|---|
| 2 years ago | ||
| 2 years ago | ||
| 2 years ago | ||
| 2 years ago | ||
| 2 years ago | ||
| 2 years ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 2 months ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 1 month ago | ||
| 7 months ago |