Analyze the cache for defects triggered by adversarial or extreme API inputs.
For each category, construct concrete inputs and trace the code path:
Weight extremes: Integer.MAX_VALUE for every entry (overflow?),
MAX_VALUE→1 delta (overflow?), 0 for all (unbounded growth?),
inconsistent weigher (divergence?).
Expiry extremes: Long.MAX_VALUE nanos (timer wheel overflow?),
0 or negative (infinite loops?), MAX→0 transitions, alternating durations.
Maximum size extremes: Long.MAX_VALUE (arithmetic overflow?),
maximumSize(0) (graceful degeneration?), maximumSize(1) (temporary oversize?).
Key/value adversarial behavior: constant hashCode(0) (sketch degeneration?),
slow equals() (lock hold explosion?), mutating hashCode (silent corruption?),
huge values (allocation failure handling?).
Concurrency extremes: 10K threads on same computeIfAbsent, puts exceeding
maintenance throughput (backpressure?), refresh storms from short refreshAfterWrite.
Frequency sketch saturation: all accesses to same key, all unique keys
(reset cost?), counter overflow beyond 4-bit limit.
Time extremes: nanoTime near Long.MAX_VALUE (wrap-around?), non-monotonic
ticker, large time jumps (timer wheel handling?).
For each issue: state input values, trace computation, state whether it causes
incorrect behavior / OOM / infinite loop / degraded performance / graceful handling.
Do not report issues requiring API contract violations (e.g., null keys)
unless the violation is undetected and causes silent corruption.
1---2name: audit-adversarial-input3description: Analyze behavior under adversarial or extreme API inputs4---56Analyze the cache for defects triggered by adversarial or extreme API inputs.78For each category, construct concrete inputs and trace the code path:9101. **Weight extremes**: Integer.MAX_VALUE for every entry (overflow?),11 MAX_VALUE→1 delta (overflow?), 0 for all (unbounded growth?),12 inconsistent weigher (divergence?).13142. **Expiry extremes**: Long.MAX_VALUE nanos (timer wheel overflow?),15 0 or negative (infinite loops?), MAX→0 transitions, alternating durations.16173. **Maximum size extremes**: Long.MAX_VALUE (arithmetic overflow?),18 maximumSize(0) (graceful degeneration?), maximumSize(1) (temporary oversize?).19204. **Key/value adversarial behavior**: constant hashCode(0) (sketch degeneration?),21 slow equals() (lock hold explosion?), mutating hashCode (silent corruption?),22 huge values (allocation failure handling?).23245. **Concurrency extremes**: 10K threads on same computeIfAbsent, puts exceeding25 maintenance throughput (backpressure?), refresh storms from short refreshAfterWrite.26276. **Frequency sketch saturation**: all accesses to same key, all unique keys28 (reset cost?), counter overflow beyond 4-bit limit.29307. **Time extremes**: nanoTime near Long.MAX_VALUE (wrap-around?), non-monotonic31 ticker, large time jumps (timer wheel handling?).3233For each issue: state input values, trace computation, state whether it causes34incorrect behavior / OOM / infinite loop / degraded performance / graceful handling.3536Do not report issues requiring API contract violations (e.g., null keys)37unless the violation is undetected and causes silent corruption.
ben-manes