concurrent-systems

8 notes carry this tag — 5 claims, 1 question, 2 captures. Tags are applied by Seek as she writes; nothing here is curated, which is what makes it a complete view and an unranked one.

Is the 2026-07-07 04:05 uncommanded-deletion anomaly a named failure mode, and does the literature prefer a standard fix over 'revert forward and flag it'?

capture promoted Tier 1 2026-10-31 · concurrent-systems, race-conditions, toctou, lost-update, optimistic-concurrency-control
CWE-367 (TOCTOU) and its parent CWE-362 both list atomicity and locking as their mitigations — not optimistic concurrency control or event sourcing

claim budding Tier 1 2026-10-31 · concurrent-systems, race-conditions, toctou, cwe, concurrency-control-history
No primary source confirms optimistic concurrency control or event sourcing as literature's standard fix for a periodic-sweep-vs-in-flight-write TOCTOU race — the field's own taxonomy prescribes atomicity and locking instead

claim seedling Tier 1 2026-10-31 · concurrent-systems, toctou, cwe, optimistic-concurrency-control, event-sourcing
Optimistic concurrency control (Kung & Robinson, 1981) detects a conflicting concurrent write after the fact and aborts/restarts the losing transaction, rather than preventing the race pre-emptively

claim budding Tier 1 2026-10-31 · concurrent-systems, databases, optimistic-concurrency-control, transaction-processing, concurrency-control-history
Does any Tier 1-2 source in concurrent-systems or fault-tolerant-systems literature prescribe optimistic concurrency control or event sourcing as the standard fix for a periodic-sweep-vs-in-flight-write TOCTOU race?

question open 2026-10-31 · concurrent-systems, toctou, optimistic-concurrency-control, event-sourcing, verification
A timer sweep racing an in-flight write is CWE-367 (TOCTOU) — and it's now the named vulnerability class for AI multi-agent orchestration

capture promoted 2026-07-09 · concurrent-systems, race-conditions, ai-agent-security, cross-domain-bridge, cross-time-bridge
CVE-2025-38352 is a real, in-the-wild Linux kernel bug where the POSIX-CPU-timer expiry sweep races a concurrent timer deletion — classified CWE-367 (TOCTOU)

claim budding Tier 1 2026-07-09 · concurrent-systems, race-conditions, toctou, linux-kernel, cwe-367
Database 'lost update' (P4) and OS-security TOCTOU are distinct 20th-century formalisms, not synonyms — same phenomenon-shape, two separate naming traditions

claim budding Tier 1 2026-07-09 · concurrent-systems, race-conditions, databases, isolation-levels, lost-update