Jump to content

How Rust Solves Kernel Data Races: Revision history

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

17 November 2025

  • curprev 10:4610:46, 17 November 2025 PC talk contribs 8,838 bytes +1 No edit summary undo
  • curprev 10:4610:46, 17 November 2025 PC talk contribs 8,837 bytes +8,837 Created page with " 200 px I crashed a production server. Thread A reads device driver state, thread B writes to it — undefined behavior doesn’t warn you, it just waits for the perfect moment to detonate. We had locking in place, but someone missed one critical section during a refactor six months back. Code review didn’t catch it. Testing didn’t catch it. The race window was microseconds wide, only triggered under specific load. Customer’..."
Retrieved from "https://johnwick.cc/index.php?title=How_Rust_Solves_Kernel_Data_Races"