OpenParable
Skip to content
← Back to skills

Audit Jmm

Testing & Quality
audit-jmm

Audit Jmm is an Agent Skill for testing & quality published in the ben-manes/caffeine repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Java Memory Model audit of all VarHandle/volatile field access modes

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/ben-manes/caffeine/blob/HEAD/.claude/skills/audit-jmm/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/audit-jmm, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Perform a Java Memory Model audit of the cache.

For every field accessed via VarHandle or Unsafe, and for every field declared volatile or accessed under synchronization:

  1. State the field name, type, and declared access mode.
  2. List every read and write with: access mode, method/line, locks held.
  3. For each (write, read) pair: state whether happens-before is guaranteed. If it depends on access mode, verify BOTH sides use compatible modes.
  4. Identify any field where:
    • Plain/opaque write paired with plain/opaque read across threads with no intervening synchronization
    • Code relies on opaque providing ordering beyond coherence
    • Volatile read on one field but non-volatile on a correlated field

Specific areas to examine:

  • writeTime: encodes both timestamp and refresh-in-progress flag
  • accessTime: is opaque access sufficient for expiration?
  • key/value fields: do value reads provide visibility of the object's fields?
  • policyWeight vs weight: correlated but updated at different times

For each issue:

  • State the specific reordering or visibility failure
  • Construct a concrete 2-thread execution
  • Verify the execution is legal under the JMM (not just TSO)

Do not report issues that only affect performance. Do not report deliberately racy patterns with documented stale-read tolerance.

Platform focus: Pay specific attention to aarch64 (ARM) memory ordering. ARM's weaker-than-TSO model exposes reordering bugs invisible on x86. Historical bug: WeakValueReference.keyReference required setRelease + storeStoreFence (not just setRelease alone) because the field is non-final and aarch64 reorders the field write after reference publication. Check for similar patterns — non-final fields published via release without a fence.