diff --git a/issues/kernel/a-log-rings-owner-is-named-only-when-logd-reads-its-registration.md b/issues/kernel/a-log-rings-owner-is-named-only-when-logd-reads-its-registration.md index 0579384cef..c759e91b59 100644 --- a/issues/kernel/a-log-rings-owner-is-named-only-when-logd-reads-its-registration.md +++ b/issues/kernel/a-log-rings-owner-is-named-only-when-logd-reads-its-registration.md @@ -1,5 +1,5 @@ --- -status: open +status: expected-red kind: defect opened: 2026-09-27 --- @@ -28,6 +28,7 @@ log_`, interleaved per round against `origin/main`'s kernel and tests: began; 0 of 5 after); - `origin/main`: 2 red of 13 (0 of 8 at 1ce71831, 2 of 5 at 16d2e645). Each red was this failure. The race is on `main`. +Also red on the orchestrator's Fast tier for PR #563 at `d6716fc7`: the same failure. The fix belongs where the owner is decided: - init names the owner itself, after the spawn and before the frame. That @@ -37,3 +38,9 @@ The fix belongs where the owner is decided: **Exit**: a child writing before the ring's owner is named cannot take the slots the owner is kept, shown by a test that makes it write in that window. +No test today covers that owner decision in `Ring::push` +(`toyos/src/log/region.rs:202`) or logd's `ring.own(pid)` +(`userland/logd/src/origin.rs:176`); `let keep = 0;` there, or deleting +`ring.own(pid)`, passes every test in the tree, so the exit's test must turn +both mutations red. Owner: `toyos/src/log/region.rs`'s `Ring::push`; held by +the orchestrator. diff --git a/src/redlist.rs b/src/redlist.rs index 301519afaf..8fb71e1968 100644 --- a/src/redlist.rs +++ b/src/redlist.rs @@ -51,6 +51,10 @@ pub const DISABLED: &[Disabled] = &[ issue: "issues/build/a-swaps-redial-races-a-hard-dial-ceiling-against-an-unbounded-guest-gap.md", }, Disabled { test: "latency_wake", issue: "issues/build/latency-wake-reds-on-the-dev-host-at-a-rate.md" }, + Disabled { + test: "log_ring_keeps_the_owners_slots", + issue: "issues/kernel/a-log-rings-owner-is-named-only-when-logd-reads-its-registration.md", + }, Disabled { test: "partition_claim_departure", issue: "issues/boot-media/partition-claim-departure-exits-clean-with-none-of-its-refusals-said.md",