Revert "block fuzz data over 100kb" #3927
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit cb1634d since https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24383 was fixed with commit df26bd1 instead.
5a0e970 to
7c20e81
Compare
|
My gut says that we should also remove/increase this check: libvips/fuzz/jpegsave_buffer_fuzzer.cc Lines 23 to 28 in bcb188f Given that it already ought to be covered by the |
|
Ah, there is an extra |
jcupitt
reviewed
Apr 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit cb1634d since https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24383 was fixed with commit df26bd1 instead.
Note that timeouts and OOMs are only reported once per fuzz target, so this may cause duplicate reports.
https://google.github.io/oss-fuzz/faq/#how-do-you-handle-timeouts-and-ooms