2 Commits

Include renames

Author	SHA1	Message	Date
Yu WatanabeandZbigniew Jędrzejewski-Szmek	7593691aad	fuzzers: add input size limits, always configure limits in two ways ... Without the size limits, oss-fuzz creates huge samples that time out. Usually this is because some of our code has bad algorithmic complexity. For data like configuration samples we don't need to care about this: non-rogue configs are rarely more than a few items, and a bit of a slowdown with a few hundred items is acceptable. This wouldn't be OK for processing of untrusted data though. We need to set the limit in two ways: through .options and in the code. The first because it nicely allows libFuzzer to avoid wasting time, and the second because fuzzers like hongfuzz and afl don't support .options. While at it, let's fix an off-by-one (65535 is the largest offset for a power-of-two size, but we're checking the size here). Co-authored-by: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>	2022-05-12 13:31:11 +02:00
Zbigniew Jędrzejewski-Szmek	82544241ba	fuzz-bootspec: limit input size ... https://oss-fuzz.com/testcase-detail/5680508182331392 has the first timeout with 811kb of input. As in the other cases, the code is known to be slow with lots of repeated entries and we're fine with that.	2022-05-11 02:12:35 +09:00