name	audit-reentrancy
description	Analyze user callbacks for re-entrancy defects (deadlock, corruption)
context	fork
agent	auditor
disable-model-invocation	true

Analyze the cache for defects caused by user callbacks re-entering the cache.

User-provided callbacks:

CacheLoader.load(key) / loadAll(keys)
CacheLoader.reload(key, oldValue)
Weigher.weigh(key, value)
Expiry.expireAfterCreate / expireAfterUpdate / expireAfterRead
RemovalListener.onRemoval(key, value, cause)
EvictionListener (synchronous variant)
Mapping functions passed to compute, computeIfAbsent, merge

For each callback:

List every lock held at the point the callback is invoked. Include: evictionLock, CHM bin lock, synchronized(node), any other.
Determine what happens if the callback calls EACH of these cache methods: get, put, remove, compute, computeIfAbsent, size, clear, cleanUp, asMap().entrySet().
For each (callback, cache method) pair where locks are held:
- Can it deadlock? (Same lock re-acquired? Lock ordering violated?)
- Can it corrupt state? (Re-entering a method mid-mutation?)
- Can it observe partially-constructed state?
If the cache defends against re-entrancy (e.g., by deferring work), explain the mechanism and verify it is complete.

For each defect: state the callback, re-entrant method, locks involved, call stack, and observable incorrect behavior.

المزيد من هذا المستودع

نفس المستودع

audit-adaptivity

ben-manes/caffeine

Audit the adaptive window hill-climber and region-resize logic for implementation defects (not algorithm quality)

2026-06-1717.7k

audit-jcache-conformance

ben-manes/caffeine

JSR-107 (JCache) spec-conformance audit

2026-06-1717.7k

audit-state-machine

ben-manes/caffeine

Audit explicit state machines (drain status, node lifecycle, async-value lifecycle) for illegal or missed transitions

2026-06-1717.7k

audit-temporal-walk

ben-manes/caffeine

Heavyweight history-mining bug audit. Walks the caffeine module's git history chronologically (oldest to HEAD), maintains a forward-tracked issue database, and surfaces concerns introduced by past commits that were never resolved. Catches bugs that snapshot mining cannot — half-fixes invisible from current state, latent+trigger pairs across multi-commit interactions, and partial refactors. Slow (model/effort-dependent; ~24h on Opus + max effort) and rare-run (every several months or before a major release).

2026-06-1717.7k

audit-sibling-divergence

ben-manes/caffeine

Differential audit comparing matched code paths that should behave identically. Spawns one auditor per sibling pair (sync/async, bounded/unbounded, view consistency, bulk vs single, generated node variants, read fast vs slow, adapter conformance) and requires a concrete witness scenario where the two paths diverge observably.

2026-06-0217.7k

audit-contract-drift

ben-manes/caffeine

Find places where documented API contracts and the implementation diverge

2026-04-2717.7k

name	audit-reentrancy
description	Analyze user callbacks for re-entrancy defects (deadlock, corruption)
context	fork
agent	auditor
disable-model-invocation	true

Analyze the cache for defects caused by user callbacks re-entering the cache.

User-provided callbacks:

CacheLoader.load(key) / loadAll(keys)
CacheLoader.reload(key, oldValue)
Weigher.weigh(key, value)
Expiry.expireAfterCreate / expireAfterUpdate / expireAfterRead
RemovalListener.onRemoval(key, value, cause)
EvictionListener (synchronous variant)
Mapping functions passed to compute, computeIfAbsent, merge

For each callback:

List every lock held at the point the callback is invoked. Include: evictionLock, CHM bin lock, synchronized(node), any other.
Determine what happens if the callback calls EACH of these cache methods: get, put, remove, compute, computeIfAbsent, size, clear, cleanUp, asMap().entrySet().
For each (callback, cache method) pair where locks are held:
- Can it deadlock? (Same lock re-acquired? Lock ordering violated?)
- Can it corrupt state? (Re-entering a method mid-mutation?)
- Can it observe partially-constructed state?
If the cache defends against re-entrancy (e.g., by deferring work), explain the mechanism and verify it is complete.

For each defect: state the callback, re-entrant method, locks involved, call stack, and observable incorrect behavior.