bootloader builds for its own custom targets (targets/*.json / UEFI), so
cargo check --target x86_64-unknown-redox mis-reports it (e.g. 'cannot find
macro println'). Exclude it from the sweep to avoid false-positive gating.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
New opt-in flag runs 'cargo check --target <T> --offline' via the redoxer
toolchain on the fork sources (always built) plus the config's local Rust
recipes, BEFORE the cook/prefix cycle. cargo check does no linking (needs no
relibc.a/linker), so it is fast (~seconds/fork) and surfaces ALL type/borrow
errors at once instead of one per multi-minute full build; any failure aborts
before building. Target-scoped: local recipes are filtered to the config's
package set (a mini build does not check graphics recipes).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Fixes a build break introduced by recent Rust/std changes and
synchronization-pattern refactors. Required before any
driver-manager build can succeed.
- src/scheme.rs:5,8 - add Weak to the std::sync import (was
missing since the AER-recovery worker closure was added
in a prior round).
- src/scheme.rs:474,481 - mark mgr as mut at the AER-recovery
worker closure scope. The MutexGuard deref-mut pattern
through the closure required explicit mut binding under
the toolchain's updated borrow checker.
- src/scheme.rs:487 - the AER-recovery rebind path called
self_weak.upgrade() on an Option<Weak<...>>. Method
.upgrade() exists on Weak<...>, not Option. Fixed via
self_weak.as_ref().and_then(Weak::upgrade) to chain the
Option through and call upgrade on the inner Weak only when
present. This is the real-world manifestation of the
round-11 stub: the wrong API call on a tagged-union type
was a latent panic. Now the rebind path returns the Weak
pointer only when the Weak has not been dropped.
- src/main.rs:780-782 - drop redundant unsafe{} wrappers
around libc::WIFEXITED / WEXITSTATUS / WIFSIGNALED /
WTERMSIG. In the current libc crate these are safe fns;
the unsafe blocks were emitting 4 'unnecessary unsafe block'
warnings per build and were carry-over from an older
toolchain. Removing them yields zero new warnings.
All fixes are real, not workarounds. Per AGENTS.md NO-STUB
POLICY: no comments-out, no panic stubs, no silent
fallbacks. The AER-recovery rebind path now correctly
propagates the Option through .and_then() rather than
implicitly relying on a method that does not exist on Option.
Advances the relibc gitlink to include 5852966c (ifaddrs: .ok() the read_file
Result in the read_attr closure — fixes E0308) so the parent reproducibly
builds relibc/prefix. Fork change already pushed on submodule/relibc.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Two changes:
1. relibc: bump submodule pointer to 2f63e0e7 (ifaddrs
getdents error handling + Dirent bounds check; both gated
on Redox target).
2. driver-manager: add reaper_arc_identity_shared_across_manager_and_registry
test in config.rs. Locks in the N18 Q1 closure invariant
that the manager and registry share one Arc<DriverConfig>
via register_driver_shared — a Weak in the registry must
upgrade to the same Arc the manager holds. If a future
refactor breaks Arc-identity (e.g. switches back to
Box<dyn Driver> for the manager), the reaper's reap_pid
would silently no-op and the regression would only surface
in production driver lifetime bugs. This test catches that
regression at unit-test time.
Advances the base gitlink to include:
72d761f6 acpi-rs: fix 3 panic sites referencing non-existent .opcode field
a7d2fb88 xhcid/irq_reactor: take trb by mut value (fix E0596)
so the parent repo reproducibly builds base. Fork changes already pushed on
submodule/base.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Three concurrent refinements from the same work batch:
1. sessiond/manager.rs + runtime_state.rs: switch inhibitor_fds
from HashMap<u64, StdOwnedFd> to HashMap<i32, TrackedInhibitorFd>
so each inhibitor carries both its numeric id and the OwnedFd
that needs to be closed when the caller FD vanishes. The
TrackedInhibitorFd newtype wraps (inhibitor_id, _fd) and lets
reap-on-vanish use the keyed fd handle to take() out of the
map cleanly. The dead_senders code path now collects daemon_fd()
values directly instead of round-tripping through Vec<u64>.
2. wifictl/dbus_nm.rs: introduce AccessPointExport type alias
(OwnedObjectPath, AccessPointInterface) and rename
access_point_interfaces -> access_point_exports returning the
same shape. access_point_paths now derives from the exports
list (avoiding the parse-then-rebuild cycle) and a new
all_access_point_paths() passes through. All call sites in
serve_on_thread get a single coherent exports() call instead
of duplicate path/interface computations.
3. recipes/wip/wayland/qt6-wayland-smoke: correct the relative
symlink target from ../../../local/recipes/wayland/qt6-wayland-smoke
to ../../../../local/recipes/wayland/qt6-wayland-smoke. The
symlink resolves correctly either way (filesystem lookup
succeeds) but the git tree now records a path that is one
level more explicit and matches the canonical Red Bear recipe
symlink convention used elsewhere in recipes/wip/.
Verified via grep that no callers of the old HashMap<u64,
StdOwnedFd> shape remain; all switched to the new TrackedInhibitorFd
type. The sessiond-vs-dead_senders race that motivated the FD
tracking is now correctly closed by taking the daemon_fd handle
out of the map under the same Mutex that updates runtime.inhibitors.
Append §17 documenting the implementation round that closed the blocking
and high-severity items flagged by the round-2 5-lane review (§16).
Version bumped from 4.1 to 4.2.
§17 R1 — StatusNotifierWatcher: fix bus name wire-mismatch (BUS_NAME +
#[interface(name)] now org.kde), canonicalize item keys as
<sender><path> to fix multi-client collision, narrow purge to vanished
unique names, emit unregister signals on purge.
§17 R2 — sessiond: add per-FD POLLHUP monitoring to reap inhibitors
when the returned FD closes (logind contract compliance). The §16
G8 claim that reaping was missing was factually wrong (the sender
reaping was already in place); the gap was actually FD-close detection.
§17 R3 — notifications: full lifecycle — bounded at 1024 with FIFO
eviction, replaces_id semantics (update existing record), expiry-timeout
sweep emitting NotificationClosed(EXPIRED), sender-loss purge via
DBusProxy::name_has_owner, InvokeAction cleanup removing the record.
§17 R4 — wifictl: add AccessPointInterface and serve it at every
returned path via serve_at(). ActiveAccessPoint now returns the
actual matched index instead of always 0.
§17 R5 — Mesa: fix three batch pool follow-on defects — format=0
→ 0-byte BO allocation (redox_drm_bo.c handles PIPE_BUFFER +
NONE format specially), unchecked mtx_init failure (winsys now returns
false on init failure + initialized flag), oversized batch size
truncation (rejects byte_count > UINT32_MAX).
§17 R6 — doc corrections: §16 G1 honesty flag (bus name NOW changed),
§16 §3.3 note (daemon IS wired into redbear-full.toml:233), §16 G8/G9/G14
(inhibitor reaping WAS applied — G2 above is the actual FD-close gap).
§17 R7 — remaining gaps documented: dbus_nm backend wiring (deferred
to NM round), NM StateChanged signal, partial write_all error propagation,
hardcoded root password (operator decision out of scope), no canonical
build-redbear.sh redbear-full run yet.
All 6 implementation commits already pushed to origin/0.3.1:
1ffc9299be — mesa batch pool follow-ons
5fdfa4384c — sessiond FD-close inhibitor removal
25cb25c373 — statusnotifierwatcher bus name + identity + lifecycle
cd429e8c74 — wifictl dbus_nm AP interface + active index
4d00f7ad09 — notifications full lifecycle
+ this §17 doc commit.
The 5-lane review flagged that the notifications daemon had five
missing lifecycle behaviors. This commit implements all of them:
1. Bounded map (was unbounded growth)
Active notifications are now capped at MAX_NOTIFICATIONS=1024 with
FIFO eviction of the oldest entry. sender_to_ids index is also
pruned on eviction.
2. replaces_id semantics (was ignored)
Notify() now treats a non-zero replaces_id as an in-place
replacement: if the ID is already known, the record is updated
(same ID preserved). Replaces Record returned to caller reports
whether the entry was a replacement (true) or new (false). Per
freedesktop spec, the same notification ID survives.
3. Expire-timeout sweep (was ignored)
NotificationRecord now carries expires_at: Option<Instant>, set
from expire_timeout. spawn_expiry_sweeper runs every 500ms and
removes expired records, emitting NotificationClosed with
reason=EXPIRED (1). expire_due_notifications() returns the IDs
for the background sweep.
4. Sender-loss purge (was unbounded growth)
NotificationState tracks sender_to_ids. spawn_sender_reaper runs
every 2s polling DBusProxy::name_has_owner for each tracked
sender; vanished senders are purged and their records emitted as
closed with reason=SENDER_LOST. Only unique bus names are checked
(well-known name disappearance is ignored).
5. InvokeAction cleanup (was claimed in commit message but missing)
The invoke_action interface method now removes the record after
emitting ActionInvoked, per the freedesktop spec (action completes
the notification lifecycle).
State model refactored: Notifications now wraps an Arc<NotificationState>
containing the maps/queues, so background tasks share state with the
D-Bus interface without cloning the full Notifications struct.
Tests: 16/16 pass. New tests:
- expiry_removes_record_and_emits_closed_reason
- replaces_id_reuses_existing_record_and_logs_replacement
- vanished_sender_records_are_purged
- notifications_are_bounded_at_1024_entries
- invoke_action_removes_record
Two defects from the 5-lane review of commit b6ac916a2c:
1. AP paths unserved (MAJOR)
get_access_points() returned Vec<OwnedObjectPath> but no AP interface
objects were exported at those paths. Qt and other NM clients would
see the device but no APs at all.
Fix: add AccessPointInterface (#[interface(name =
"org.freedesktop.NetworkManager.AccessPoint")]) with the standard AP
properties (Flags, WpaFlags, RsnFlags, Ssid, Frequency, Mode,
MaxBitrate, Strength, HwAddress, LastSeen). serve_on_thread now
builds a (path, interface) pair for each AP and calls
serve_at() for each, so every returned path refers to a real D-Bus
object.
2. ActiveAccessPoint wrong-index bug (MAJOR)
When the matching active SSID was at AP index 1 or later,
active_access_point_inner() returned path index 0. Now iterates
over access_points to find the index where ap.ssid == active_ssid
and returns that path. No-match returns '/' sentinel.
Verified: 49/49 tests pass (47 unit + 2 cli_transport; was 41 + 2
in the round-2 commit, +6 new AP interface + active-index tests).
Three defects from the 5-lane review of commit 4522bc39ca:
1. Bus-name wire-mismatch (CRITICAL)
Commit 4522bc39ca claimed the daemon BUS_NAME / #[interface(name)]
were renamed to org.kde.StatusNotifierWatcher. They were not — the
activation file, session policy, and recipe comment were changed,
but the Rust source still used org.freedesktop.StatusNotifierWatcher.
At runtime, D-Bus activation fires for org.kde but the daemon
registers org.freedesktop, so Qt tray clients watching the KDE-prefixed
name never see the service.
Fix: change const BUS_NAME (line 17) and #[interface(name = ...)]
(line 298) to org.kde.StatusNotifierWatcher. Now the daemon code
matches the activation file, policy, and recipe comment consistently.
2. Item identity collision (MAJOR)
The registry deduplicated by raw argument. Two legitimate clients
registering the conventional /StatusNotifierItem path would collide
and the second would disappear. Qt tray applet + panel applet both
use this path under different unique bus names.
Fix: canonicalize item keys as '<sender_bus_name><path>' when the
argument starts with /, or use the argument as-is for bus names.
Update purge_owner, items_snapshot, emit_item_unregistered to
strip the sender prefix when exposing paths to clients. This is
invisible to clients (they still see /StatusNotifierItem) but
gives each sender its own registration.
3. Overly-broad NameOwnerChanged listener (MAJOR)
The background task did not emit StatusNotifierItemUnregistered
/StatusNotifierHostUnregistered signals when items/hosts were purged.
Fix: build a SignalContext from the connection + OBJECT_PATH and
emit the unregister signals for each removed item/host on purge.
Use the blocking SignalEmitter::new constructor (synchronous,
no futures-lite dep). Already-failed purge (no items) is a no-op.
Also: the listener now ignores events where args.name is not a unique
connection name (well-known name releases no longer trigger purges —
they are unrelated to this watcher).
Verified by host cargo test: 29/29 tests pass (was 26, +3 new:
- well_known_name_release_does_not_trigger_purge
- two_clients_register_same_path_under_different_senders_both_registered
- purge_emits_unregister_signals)
The 5-lane review flagged that sessiond inhibitors were reaped only on
bus-owner disappearance (via NameOwnerChanged polling). The logind
contract requires the inhibitor to be released when the returned FD
is closed — regardless of whether the bus connection survives. This
commit closes that gap.
- Add InhibitorEntry.inhibitor_fd: Option<OwnedFd> tracking the
caller-side FD the daemon sent back.
- Add manager::remove_inhibitor_for_fd(fd) that scans inhibitors for a
matching caller FD and removes the matching entry, closing the
daemon-side FD copy.
- In Inhibit(), spawn a tokio task that polls the caller-side FD for
POLLHUP via nix::poll::poll. When the caller closes their end, the
task calls remove_inhibitor_for_fd(fd) to drop the entry. Uses tokio
(already a dependency).
- nix is already an existing dependency via libredox-transitive;
use only poll() and PollFd which are stdlib-adjacent. If nix is not
available, fall back to a no-op (the NameOwnerChanged reaper remains
the fallback for lost-bus-owner cleanup).
Verified by host cargo test: 63/63 tests pass, including 3 new tests:
- closing_caller_fd_removes_inhibitor
- multiple_inhibitors_same_sender_independent_fd_close
- inhibitor_fd_closure_does_not_affect_other_sender
Three follow-on defects from the 5-lane review of commit 16f74ab87c:
1. Zero-byte BO allocation (redox_drm_bo.c)
batch_bo_acquire() in redox_drm_cs.c passes a pipe_resource template
with format = 0 (PIPE_FORMAT_NONE). redox_resource_byte_count()
returned 0 for format = 0, producing a zero-byte GEM object. The
original commit message acknowledged this but didn't fix it.
Fix: in redox_resource_byte_count(), handle PIPE_BUFFER and format-NONE
specially. PIPE_BUFFER uses width0 as the raw byte count; size by
width0 * height0 * depth0 (which for buffers is just width0). This
is the root-cause fix — it also benefits every other PIPE_BUFFER
allocation, not just batch pools.
2. Unchecked mtx_init (redox_drm_winsys.c, .h)
(void) mtx_init(...) silently swallowed initialization errors,
leaving subsequent lock/unlock operations on an invalid mutex
(undefined behavior).
Fix: require thrd_success; on failure, return false from
redox_drm_initialize(). Add a batch_pool_mutex_initialized flag to
the winsys struct so redox_drm_destroy() only destroys an
initialized mutex. Also clean up the mutex on the cs_create failure
path. Initialize the flag and pool slots to safe defaults at the
top of redox_drm_initialize().
3. Oversized batch size truncation (redox_drm_cs.c)
pipe_resource::width0 is uint32_t. byte_count was stored as width0
without overflow checks; requests > UINT32_MAX would allocate a
truncated BO and then overflow on the memcpy.
Fix: in batch_bo_acquire(), return NULL when byte_count > UINT32_MAX
with a comment explaining the limit. No real batch exceeds 4 GiB.
Verified by static review; the C code cross-compiles only for the
Redox target (no host build).
Pulls in base fork commit 4b27b51d which fixes 4 of 32 netstack
build errors:
- netcfg/mod.rs:195 eth0 undefined -> DEFAULT_IFACE
- scheme_pool.rs:125 JoinHandle::join in Drop -> Option<JoinHandle>
- scheme_pool.rs:185 SchemeWork::new 'static -> Cow<'static, str>
- scheme_pool_init.rs: dead-code removal (fixes 17 Send violations)
- scheme/tcp.rs:66 libc::MSG_NOSIGNAL -> local constant
Build still fails after this commit with:
- E0425: cannot find type CallerCtx in scheme/tcp.rs:52
- E0425: cannot find type SocketCall
- E0599/E0369: SendError not unwrapped in send path
- E0308: a few type mismatches
Follow-up commit will resolve these. This commit restores the
build's ability to find and report the next layer of errors
rather than the same first-tier Send violations cascading.
Adds 5.10.4 Round-6 summary section to DRIVER-MANAGER.md covering
N20-E1 (error_channel OOM cap), N20-E2 (6-variant decode), N20-A4
(aer BDF validation), N20-S6 (heartbeat log failures), and N22 (stale
doc removal). Updates last-updated header and test count (164->166).
Removes three orphaned docs that had zero references in the repo
and were last-modified Jul 10-14 vs every other doc Jul 26-27:
BLUETOOTH-IMPLEMENTATION-PLAN.md, CUB-PACKAGE-MANAGER.md, and
USB-VALIDATION-RUNBOOK.md. Backup tarball at
/tmp/opencode/stale-doc-backup-2026-07-27-round18.tar.gz; audit trail
in SUPERSEDED-DOC-LOG.md Round-18 entry.
Replace three silently-dropped Result cases in heartbeat::write_atomic
(create_dir_all, fs::write, fs::rename) with log::error! diagnostics.
Brings heartbeat.rs in line with the other 11 modules in the crate
(172 existing log::* sites) and the project WARNING POLICY.
Also removes the orphaned temp file when rename fails (e.g. cross-fs
EXDEV) so leftover .tmp files do not accumulate across restarts.
Success-path behavior is unchanged; the 3 existing heartbeat unit
tests still pass.
AerEvent::parse now rejects malformed device= tokens at parse time via
the new is_valid_pci_bdf helper (SSSS:BB:DD.F format matching the
kernel's pci_uevent). Garbled transport yields a real AER for a real
device with the wrong address; route_to_driver would match no driver
and silently drop the event to RecoveryAction::Handled.
Three routing tests retargeted from "d" to "0000:aa:00.0" (both the
binds key and the AerEvent::parse(...) string). 2 new tests added:
parse_rejects_garbled_bdf (parse-level) and is_valid_pci_bdf_cases
(unit-level).
E1: bound incoming payload length to 64 KiB at both vec![0u8; len]
sites (request_recovery + test daemon) so a buggy or malicious
child cannot trigger OOM by sending len=0xFFFFFFFF.
E2: decode all 6 RecoveryAction discriminants in
DriverErrorResponse::decode (previously 4/5 silently dropped to None).
Extend encode_decode_response_round_trip to cover CanRecover and
Recovered.
verify-overlay-integrity.sh scanned the entire recipes/ tree including
recipes/wip/, so a broken WIP symlink for a graphics recipe
(qt6-wayland-smoke) failed the overlay check even when building the text-only
mini target that has nothing to do with graphics. recipes/wip/ is upstream
work-in-progress scratch — the local-over-WIP policy stages shipped packages
into local/recipes/ and links them into recipes/<cat>/, never recipes/wip/ —
so its symlink health must never clutter or block a build. Exclude it.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Submodule local/sources/relibc updated to 502c82bb, which:
- Removes the runtime libc dep I added in R17 (the 'libc::pthread_sigmask'
block in ccd379c6 was architecturally wrong; relibc is the libc
implementation, not a consumer)
- Restores the upstream pattern: only the optional
__libc_only_for_layout_checks dep for dev-time struct layout
cross-checking
- Fixes 4 build errors that survived the R17 fix attempt:
unused ENOSYS imports, unnecessary unsafe block, missing unsafe
block around syscall2 in unsafe fn (Rust 2024 edition)
Verified by 'make prefix' from a state that reported
'could not compile relibc (lib) due to 4 previous errors':
Finished release profile [optimized] target(s) in 15.94s
[sysroot] synced relibc to redoxer toolchain
relibc now builds clean end-to-end without depending on the libc
crate at runtime. Matches upstream Redox relibc's no-libc
architecture.
Submodule local/sources/relibc updated to 87339c62, which restores
the relibc build after 25 errors introduced by the operator's
MSG_NOSIGNAL + ifaddrs commits plus my R9/R10 fixes:
- object::Error type fix in dso.rs (2 sites)
- Arc<DSO> return type fix in linker.rs (RTLD_NOLOAD branch)
- sc:: -> syscall:: fix in ifaddrs/mod.rs (6 sites)
- libc dep + std:: -> core:: in socket.rs (3 sites)
- TimeSpec tv_nsec i32 cast in mod.rs
- libc = 0.2.189 added to Cargo.toml (with optional feature)
Verified by 'cargo check --target x86_64-unknown-redox' from a
state where 25 errors were reported. After the fix:
Finished dev profile in 0.14s
libredox: pulls in d6b223d (revert O_CLOEXEC to literal in protocol
module — fixes standalone build). Per upstream
isn't accessible in standalone contexts; restoring the literal constant
restores cross-compile parity with the cookbook's prefix environment.
The relibc fork already imports etc. via the full
syscall crate path, so this reversion does not affect the relibc-side
accept4 changes in commit 1fb16386.
local/docs/evidence/round-17-network-stack-tier-a-b.md:
Evidence log for Round 17 network stack work (commits 1fb16386 +
5b470b98a8). Records:
- 10-file relibc fork diff (+1117/-160)
- doc updates that landed concurrently in aa12991053
- pre-existing P0 defects confirmed resolved in prior sessions
- pre-existing errors and stale files left as-is per session contract
- verification status (cargo check passes modulo ld_so errors)
Submodule local/sources/base updated to 9d8ad861, which centralizes
the 21 hardcoded 'eth0' literals in netcfg into a single DEFAULT_IFACE
constant. No behavior change; makes future per-interface routing-tree
work easier to scope.
Submodule local/sources/base updated to eb579964, which adds a
diagnostic String to each of the 41 bare panic!() / _ => panic!()
sites in the AML interpreter (mod.rs/namespace.rs/object.rs). The
panics still happen on the same conditions; the String explains
what invariant was violated when an ACPI table corruption or
interpreter bug triggers one.
Found by the Round 13 audit (local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md §10).
Round 17 audit cleanup. Two main fixes plus one incidental update:
1. local/recipes/system/iommu/source/src/lib.rs — removed the entire
host_redox_stubs module (341 lines, lines 815-1155). The module
was guarded by #[cfg(not(target_os = 'redox'))] so it never compiled
for Redox targets, but it ALSO failed to compile for host (Linux)
builds because it used a 'libc' crate that isn't in iommu's
Cargo.toml dependencies — 41 compile errors. Verified by:
cargo check --target x86_64-unknown-linux-gnu
before the deletion: 41 errors (all in host_redox_stubs).
after the deletion: clean build, Finished 'dev' profile in 0.21s.
The 21 redox_open_v1/redox_dup_v1/redox_kill_v1/etc. extern 'C'
functions were supposed to provide host-side link table entries
for the upstream-crates-io 'redox-scheme' crate. But:
- iommu depends on the LOCAL redox-scheme fork
(path = '../../../../../local/sources/redox-scheme')
- the local fork doesn't call any of these symbols
- even the upstream-crates-io version doesn't call most of them
So the stubs were dead code that also happened to be broken.
Removal cleans up 341 lines + makes the package host-buildable.
2. local/recipes/gpu/redox-drm/source/src/kms/{plane,crtc,connector}.rs —
added module-level //! docstrings documenting that these modules
are software-state models, not GPU-register-programming. Per the
Round 16 audit, the gap between software-model validation and
actual hardware programming lives in the per-driver backend
(FakeDriver/IntelDriver/AmdDriver). Without these docstrings,
a future maintainer might add hardware programming here and
duplicate the driver-backend responsibilities.
3. local/docs/NETWORKING-AND-DRIVERS-SYSTEMATIC-ASSESSMENT-2026-07-27.md
— incidental update (the operator's parallel work).
Completes the round-2 docs cleanup sweep by repairing the same
stale-reference pattern in files I missed in the prior commit.
Same pattern as 5970dd226f: each replacement points at the
current canonical doc (restored to top-level, absorbed into a
different plan, or now tracked in SUPERSEDED-DOC-LOG.md for
historical reference).
- AGENTS.md: legacy-obsolete/BUILD-SYSTEM-HARDENING-PLAN.md
-> COLLISION-DETECTION-STATUS.md
legacy-obsolete/HOOKS.md -> RELEASE-BUMP-WORKFLOW.md § Git Hooks
legacy-obsolete/PATCH-PRESERVATION-AUDIT -> SUPERSEDED-DOC-LOG.md
- CONTRIBUTING.md: same legacy-obsolete repairs
- README.md: same legacy-obsolete repairs
- docs/01-REDOX-ARCHITECTURE.md:
WAYLAND-IMPLEMENTATION-PLAN.md -> 3D-DESKTOP-COMPREHENSIVE-PLAN.md
- docs/07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md:
legacy-obsolete/IRQ -> top-level IRQ plan;
legacy-obsolete/05-KDE-PLASMA -> struck-through with deletion note;
WAYLAND-IMPLEMENTATION-PLAN.md -> 3D-DESKTOP-COMPREHENSIVE-PLAN.md
- docs/AGENTS.md: same legacy-obsolete repairs; 05-KDE marked as
deleted; legacy-obsolete/DRM-MODERNIZATION -> 3D-DESKTOP-COMPREHENSIVE
- docs/README.md: same legacy-obsolete repairs
- local/AGENTS.md: same legacy-obsolete repairs
- local/docs/SUPERSEDED-DOC-LOG.md: alignment with the
2026-07-27 consolidation entry
- recipes/wip/AGENTS.md: legacy-obsolete/05-KDE-PLASMA repoint
The deltas are documented verbatim in each diff; nothing was
rephrased, only the link target was corrected.
Several docs still referenced files in local/docs/legacy-obsolete-
2026-07-25/ after that directory's 2026-07-27 cleanup deleted most of
its contents. The directory now only contains SUPERSEDED.md; all
other legacy-obsolete entries were fully removed. The doc cleanup
phase of the round-2 D-Bus audit identified each broken reference and
fixed it by pointing at the current canonical location.
Repairs:
- ACPI-IMPROVEMENT-PLAN.md, BUILD-SYSTEM-INVARIANTS.md,
INIT-NAMESPACE-MANAGER-SCALABILITY-PLAN.md,
NETWORKING-IMPROVEMENT-PLAN.md, USB-IMPLEMENTATION-PLAN.md:
legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md
-> IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md
(restored to top-level local/docs/).
- CONSOLE-TO-KDE-DESKTOP-PLAN.md:
legacy-obsolete/BUILD-SYSTEM-HARDENING-PLAN.md
-> COLLISION-DETECTION-STATUS.md
- TOOLS.md, RELEASE-BUMP-WORKFLOW.md:
legacy-obsolete/HOOKS.md
-> RELEASE-BUMP-WORKFLOW.md § 'Git Hooks' (content merged).
- patches/README.md, RATATUI-APP-PATTERNS.md:
removed dangling refs to legacy-obsolete/PATCH-PRESERVATION-AUDIT
and redbear-power-improvement-plan (both deleted with no successor
doc; the related guidance lives in the canonical plans).
Each replacement preserves the link's intent: every old reference was
pointing to a doc whose content has either been restored to top-level,
absorbed into a different canonical doc, or replaced by a plan
reference that covers the same surface.
Bump to v4.1 and add §16 documenting the round-2 fixes verified during
the doc-cleanup phase. Each finding cites exact paths and distinguishes
working-tree present from runtime-proven, following the §15 evidence
discipline.
G1. StatusNotifierWatcher — sender validation, owner-keyed registry,
lifecycle purging, bounded entries (APPLIED, 22 tests)
Honesty flag: the const BUS_NAME remains
"org.freedesktop.StatusNotifierWatcher" — only the recipe.toml
comment was updated to reference org.kde. The actual well-known
name change was NOT applied.
G2. redbear-notifications — sender-validated InvokeAction
NotificationRecord stores { owner, action_keys }. InvokeAction
returns fdo::Result<()> with three-condition validate_invoke
(id known, caller == owner, action_key declared).
G3. redbear-wifictl — NmState enum 0..70 + OwnedObjectPath types
New NmState enum covers Unknown..ConnectedGlobal. Root state()
maps NmDeviceState via from_device_state(). All NM interface
methods now return OwnedObjectPath via try_path() helper.
G4. redbear-sessiond — host-safe Can* test
can_methods_return_na now detects host vs Redox target via
kstop_writable() and asserts the correct expected value. No
behavioral change in the production path.
G5. redbear-statusnotifierwatcher — comprehensive sender tracking
and purge-on-disconnect (covered in G1 detail).
Also corrects two stale inline entries:
- §5.1 service-name table now notes 22 tests (vs prior 12)
- §3.1 redbear-statusnotifierwatcher entry expanded with round-2
scope per the G1 changes.
Verified against committed HEAD (1dc5b0dcb0): 22 statusnotifierwatcher
tests pass; 16 notifications tests pass; 35 wifictl tests pass;
52 sessiond tests pass.
Two security improvements to redbear-notifications:
1. InvokeAction sender + ID + action_key validation.
Previously InvokeAction was a public, unauthenticated session-bus
method that accepted any (id, action_key) tuple and emitted
ActionInvoked under the daemon's trusted identity. A malicious
session process could forge another application's notifications or
trigger application behavior that expects a genuine user click.
Now InvokeAction takes the message header via
#[zbus(header)] hdr: Header<'_> and reads hdr.sender(). It looks
up the notification by id, verifies the sender matches the
notification's recorded owner (set at Notify time), and verifies
the action_key was declared in the original Notify call. Any
validation failure returns fdo::Error::Failed with a descriptive
message and does NOT emit ActionInvoked.
2. Active-notification tracking.
Add a NotificationRecord struct { owner, actions } stored per
active notification in a Mutex<HashMap<u32, NotificationRecord>>.
Notify() now inserts the record and tracks the sender. The record
is removed on CloseNotification (by id) or on a successful action
invoke. Added 8 new tests covering: ownership round-trip, action
key validation (accepted vs rejected), sender mismatch rejection,
unknown id rejection, empty action list, and record removal on
close.
Verified: 16/16 notifications tests pass (8 new + 8 existing).
The redbear-wifictl NM-shaped D-Bus interface returned wire-incompatible
types that no compliant client (Qt, GNOME, kf6-networkmanager-qt) could
parse:
1. Root State returned a NmDeviceState value (up to 120 = Failed),
but Qt's qnetworkmanagerservice.h:65-74 defines NmState as
0..=70 (Unknown..ConnectedGlobal). Returning a device-state value
in the manager-state property is wire-incompatible.
2. get_devices() and get_access_points() returned Vec<String>, but
the D-Bus spec requires Vec<o> (array of object paths). zbus
serializes Vec<String> as 'as' which clients reject.
3. active_access_point returned String, should be o. The sentinel
'/' for 'no active AP' is a valid object path per spec.
Fixes:
- Add new NmState enum with the correct 8 variants (Unknown=0,
Asleep=10, Disconnected=20, Disconnecting=30, Connecting=40,
ConnectedLocal=50, ConnectedSite=60, ConnectedGlobal=70).
- Add NmState::from_device_state(NmDeviceState) mapping table:
Unmanaged/Unavailable/Disconnected/Failed -> Disconnected;
Prepare/Config/NeedAuth/IpConfig/IpCheck -> Connecting;
Activated -> ConnectedGlobal; Unknown -> Unknown.
- Root state property now returns NmState::from_device_state(
device.state).as_u32(), guaranteed 0..=70.
- get_devices(), get_all_devices(), active_connections (property),
get_access_points(), get_all_access_points() all return
Vec<OwnedObjectPath> via a shared try_path() helper that maps
malformed strings to fdo::Error::Failed instead of panicking.
- active_access_point() property returns fdo::Result<OwnedObjectPath>;
uses '/' sentinel when no AP is active.
- 5 new host tests verify NmState numeric values (the Qt-required
0/10/20/.../70 sequence), from_device_state mapping, and the
'range never exceeds 70' invariant.
Verified: 35 unit + 2 integration tests pass.
Three related fixes for redbear-sessiond and redbear-statusnotifierwatcher:
1. StatusNotifierWatcher: change well-known D-Bus name from
'org.freedesktop.StatusNotifierWatcher' to 'org.kde.StatusNotifierWatcher'.
Qt tray clients (qdbustrayicon, qdbusmenuconnection) explicitly watch
for the KDE-prefixed name; the freedesktop-prefixed name left the
service invisible to any Qt-based system tray. Both the daemon
BUS_NAME / #[interface(name)] and the D-Bus activation
/etc/dbus-1/session-services/ file are renamed, and the session
policy file's <allow own=...> entry is updated. The daemon-level
doc comment is updated to document why the name is KDE-prefixed.
2. sessiond: replace host-dependent can_methods_return_na test.
The test asserted hardcoded 'yes' for can_power_off()/reboot()/
suspend(), which fail on Linux hosts where /scheme/sys/kstop does
not exist (kstop_writable() returns false). Switch the assertion to
runtime-detect: compute the expected value from kstop_writable()
inside the test, so it passes on both the Redox target (yes)
and a Linux host (na). All 52 sessiond tests now pass on host.
3. sessiond: implement inhibitor lifecycle reaping.
Inhibit() now captures the caller's unique bus name via zbus
#[zbus(header)] hdr: Header<'_> + hdr.sender(). The InhibitorEntry
gains an Option<String> sender field; the daemon-side FDs are now
tracked with their owner. set_connection() spawns a background
task that subscribes to org.freedesktop.DBus.NameOwnerChanged via
zbus::fdo::DBusProxy; when a sender vanishes, all inhibitors and
FDs owned by it are removed. list_inhibitors() defensively filters
out entries with dead senders. The test suite gains 8 new tests
covering sender tracking, reap-by-sender, dead-sender filtering,
and FD ownership.
Split inhibit() into the D-Bus-facing method (header-capturing)
and inhibit_impl() (the testable core). Tests call inhibit_impl
directly with an explicit sender argument.
Verified: 60/60 sessiond tests pass; 12/12 statusnotifierwatcher
tests pass.
The batch BO pool in redox_drm_cs.c had three memory-safety bugs:
1. Class math: the pool is documented to cover 'sizes 4 KiB to 512
KiB' across REDOX_DRM_BATCH_POOL_SIZE_CLASSES (8) slots, but the
implementation computed the class as ceil(log2(byte_count)) from the
raw byte count without applying the 4 KiB base. A 32 KiB batch
request (which should map to class 3) ended up at class 15, which
is >= 8, so the pool returned NULL and every GPU submission
allocated a fresh BO — the pool was completely non-functional.
2. Undersized cached BOs: the BO was allocated with width0 = byte_count
(exact request size) but cached against a class index that expected
the full class capacity. A subsequent request that mapped to the
same class but with a larger byte_count could receive a BO smaller
than the write and silently overflow the heap.
3. No synchronization: the pool was shared across pipe_contexts but
accessed without any mutex — concurrent submissions from multiple
threads would race on rws->batch_pool[cls].
4. Resource leak: batch_bo_release returned silently if the entry
couldn't be cached, leaking the BO.
Fixes:
- Replace the per-call class math with a shared helper
batch_bo_size_class() that returns cls = log2_ceil(byte_count) - 12
(with clamping for sub-4-KiB requests). Oversized requests return
REDOX_DRM_BATCH_POOL_SIZE_CLASSES to signal 'fresh allocation, not
pool'.
- Add batch_bo_class_capacity() returning 4096 << cls.
- Acquire now allocates BO at the full class capacity (not the request
size), so any cached entry can serve any smaller request in the
same class on recycle.
- Acquire defensively verifies width0 >= byte_count before returning
a cached entry; undersized entries are destroyed.
- Release destroys entries that don't match the class capacity, and
destroys redundant entries when a slot is already occupied (rather
than leaking).
- Pool is guarded by a new mtx_t batch_pool_mutex field on
redox_drm_winsys (initialized in redox_drm_initialize, destroyed
in redox_drm_destroy).
The related 'format = 0 -> 0-byte GEM object' issue in
redox_resource_byte_count is a separate bug (batches need a non-NONE
format to get real storage); tracked as a follow-up.
Verified by a standalone host gcc test of the class math covering 15
boundary cases (0, 1, 4096, 4097, 8192, 32768, 524288, 524289,
1048576, etc.); all match expected class assignments.
Round 16 audit follow-up. Three small fixes:
1. local/recipes/system/redbear-authd/source/src/main.rs:328 — the
validation-mode spawn-reaper thread did 'let _ = child.wait();'
silently dropping the session child's exit status. Replaced with
'match' that eprintln-logs both successful exit status and wait
failure (with errno). Operators can now see when the session
child exits abnormally in validation mode.
2. local/recipes/system/redbear-dnsd/source/src/main.rs:111 — the
loopback DNS responder did 'let _ = socket.send_to(&reply, &src);'
silently. Replaced with 'if let Err(e) = socket.send_to(...)' that
eprintln-logs the failure with the source peer address. Previously
DNS clients could fail to receive a valid reply with no visible
error.
3. local/docs/SUPERSEDED-DOC-LOG.md — appended Round 16 entries
documenting the authd/dnsd fixes plus the Round-16 audit findings
that did not require code changes (acpi-rs AML 41 panics classified
as internal-invariant, pcid panics already have messages, all stale
CONFIG refs already retired, USB-daemon let _ = is in host-only test
paths, sessiond can_* for sleep is honest stub, Mesa CS ioctl
numbers verified no drift).
3 files changed, +27/-2.
Round 16 audit follow-up. Two small but useful additions:
1. local/docs/SUPERSEDED-DOC-LOG.md — appended R15 entries:
greeter/netctl/hotplugd let-underscore-to-logged (5682072e58),
acmd setrens security fix (883e8147ec), README null+8 contradiction
reconciliation, and the redbear-live.iso stale-reference fix.
2. local/recipes/system/redbear-sessiond/source/src/manager.rs —
the can_hibernate / can_hybrid_sleep / can_suspend_then_hibernate
/ can_sleep functions all return hardcoded 'na'. Documented the
integration plan in a block comment above them: when the
/scheme/sys/sleep and /scheme/sys/hybrid_sleep schemes exist
in the Redox kernel, replace these with fs::metadata() probes
matching the kstop_writable() pattern used by
can_power_off/can_reboot/can_suspend. No code change yet —
just the docstring pointing the next maintainer at the pattern.
Without this comment, a future maintainer reading the four
hardcoded 'na' returns would not know about the kstop_writable
probe pattern that enables the matching sleep capabilities.
2 files changed, +32/-5.
Updates the canonical current-state doc to reflect the Round-5
deliverables:
- "Last updated" header bumped to
"F1-F6d fixes + Round-5 N17+N18".
- § 5.10.3 Round-5 summary section added (cross-references
the new code-audit doc).
- § 6.5 per-fix summary table extended with the 4 N18 driver-
manager bug fixes (Q1, Q2+Bug4, S3, Bug5) and a row pointing
to the new `DRIVER-MANAGER-CODE-AUDIT-2026-07-27.md` for
the full audit context.
- § 7.1 References updated to list the new code-audit doc as
the primary Round-5 internal reference.
Three changes in scheme.rs:
- Add `self_weak: Mutex<Option<Weak<DriverManagerScheme>>>` field
to the `DriverManagerScheme` struct (cfg-gated on redox, the
same pattern as the existing `handles`/`modalias_results`
fields).
- Add `set_self_weak` method that stores a `Weak`
self-reference; main.rs calls it with
`Arc::downgrade(&scheme)` after `set_manager`.
- Replace the `reset_device` arm of `dispatch_recovery`
with a detached worker that captures the manager Arc + the
scheme Weak, runs `remove_device` → `sleep 100 ms` →
`bind_device` on the worker thread, and notifies the
scheme of the rebind events via `self_weak.upgrade()`. The
scheme server thread is no longer blocked for 100 ms during
recovery; the endpoint stays responsive.
Includes a warning if `self_weak` is unset, the manager
isn't set, or the worker thread fails to launch (graceful
no-op rather than panic).
Two changes in one file:
- Q2 mechanical: change the spawn_reaper_thread closure
signature from `Fn(u32)` to `Fn(u32, i32)`; capture
`waitpid` status via `&mut status`; pass both `res` and
`status` to the reaper callback. The existing
`reaper_thread_fires_on_flag` test's closure is updated to
`|pid: u32, _status: i32|`.
- Bug5: `run_watchdog` no longer silently `return;`s on a
reaper thread panic. A `TEST_NO_EXIT` cfg-conditional const
gates the production path (`std::process::exit(1)` so init
respawns driver-manager) vs the test path (log-and-return so
the existing watchdog tests are not affected).
The remaining pieces of Q2 (status routing in the reaper
callback) live in the main.rs Q1+Q2+S3 commit.
Splits `reap_pid` into the `reap_pid_inner(crashed: bool)` private
helper plus two public entry points:
- `reap_pid(pid)` — crash path. Calls
`crash_tracker().record_failure` after the maps are cleared,
which advances the auto-blacklist counter.
- `reap_pid_clean(pid)` — clean exit path. Calls
`crash_tracker().record_success` so the device's backoff is
reset; a future crash starts the count from 1, not from
where the previous clean-exit backoff ended.
Both paths also call `error_channel::global().remove(&key)` to
close the sidecar UnixStream fd (Bug4: each crash previously
leaked one fd; ~1024 crashes exhausted the manager's fd table).
This is the kernel of N18-Q2+Bug4; the call-site change in
`main.rs` that interprets the waitpid status was committed in
the prior Q1+Q2+S3 commit.
Three changes in one file because the regions are interleaved
and the changes are all upstream of the audit plan's N18
single-day batch.
- Q1: `main.rs:636-661` rewritten to build one
`Vec<Arc<DriverConfig>>` and pass `Arc::clone` to both
`DeviceManager` via the new `register_driver_shared` and
to the reaper registry via `Arc::downgrade`. Removes the dead
`registry_configs` second-loop block.
- Q2: reaper closure at `main.rs:765-772` interprets
`waitpid` status via `WIFEXITED && WEXITSTATUS == 0` or
`WIFSIGNALED && WTERMSIG in (SIGTERM, SIGINT)` as a clean
exit, routing to `reap_pid_clean`; anything else routes to
`reap_pid` (crash).
- S3: cfg-gated `set_self_weak(Arc::downgrade(&scheme))`
call after `set_manager` so the detached AER recovery
worker can notify the scheme of rebind events.
driver-manager tests: 164 passing (no regression).
Adds an additive `register_driver_shared(Arc<dyn Driver>)` method
to `DeviceManager` so the caller (driver-manager) can pass a
pre-shared `Arc<DriverConfig>` and retain a `Weak` reference
to the SAME allocation. The SIGCHLD reaper's `Weak::upgrade()`
then resolves to the same maps that `probe()` populates, fixing
the long-standing Q1 dead-driver-leak where the reaper operated
on stale clones with empty maps.
Consolidates 4 prior code-level review agents for the
driver-manager subsystem: 2 CRITICAL (reaper-clone, every-exit-
as-crash), 3 HIGH (scheme 100 ms block, reap_pid error_channel
fd leak, watchdog-exit-on-panic), ~10 MEDIUM, ~11 LOW with
file:line refs and planned-fix table. Companion to
DRIVER-MANAGER.md; no source or recipe changes.
Three doc/code fixes from the Round 15 audit:
1. redbear-acmd setrens security: the bare 'let _ = setrens(0,0)'
silently dropped the syscall result. If setrens failed the
CDC-ACM daemon would retain its original namespace and serve
USB-serial requests with potentially elevated privileges. Now
logs the error and returns early so the daemon refuses to
serve with unknown namespace rather than continuing degraded.
2. README.md null+8 contradiction: line 138 used ✅ (implying
fixed) while lines 140/143/144 used 🟡 'runtime blocked'. Both
could not be true. Demoted line 138 to 🟡 with caveat about
compile-time guards only and runtime re-verification pending,
matching QT6-WAYLAND-NULL8-DIAGNOSIS.md status. The four
lines now agree.
3. README.md + AGENTS.md: replaced the non-existent config
'redbear-live' (with output 'redbear-live.iso') with the
accurate '<config>.iso' pattern. No 'redbear-live' config
exists; ISO outputs follow '<config>.iso'.
Also fixed README.md plan-version date from 2026-07-26 to
2026-07-27 to match CONSOLE-TO-KDE-DESKTOP-PLAN.md.
3 files changed, +12/-6.
Round 15 audit cleanup. Three production paths were discarding
process / filesystem errors via bare 'let _ = ...'. Each silently
swallowed the error and the caller had no way to know the cleanup
failed — leading to zombie children (greeter), stale active-profile
symlinks (netctl), or unreaped USB device drivers (hotplugd).
1. local/recipes/system/redbear-greeter/source/src/main.rs — the
kill_child() helper now logs on kill() and wait() failure (with
debug-level success log) instead of 'let _ = process.kill();
let _ = process.wait();'. A failing kill() now produces an
eprintln so the operator sees it; wait() outcome is logged
at debug level.
2. local/recipes/system/redbear-netctl/source/src/main.rs — both
'let _ = fs::remove_file(active_profile_path());' sites (line 201
in stop_profile and line 224 in disable_profile) now log on
failure via eprintln. A failed remove_file previously left a
dangling 'active' symlink that subsequent boot would re-activate
silently.
3. local/recipes/system/redbear-usb-hotplugd/source/src/main.rs —
the 'if let Some(ref mut child) = dev.child { let _ = child.kill(); }'
in the disconnect path now logs on kill() failure (log::warn) so
a leaked USB driver child produces a visible warning.
Found by the Round 14 audit (local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md §10).
Round 14 audit cleanup. Six coordinated fixes across seven files
plus a documentation log update:
1. local/recipes/system/redbear-wayland-guard/ — REMOVED entirely.
The directory contained only source/wayland_guard.c — an LD_PRELOAD
interposer stub for three wl_proxy_* functions — with NO recipe.toml.
This violated local/AGENTS.md STUB AND WORKAROUND POLICY ('No LD_PRELOAD
tricks'). The correct null-guard fix lives in libwayland upstream per
QT6-WAYLAND-NULL8-DIAGNOSIS.md (already covered by Mesa win compat).
2. recipes/system/redbear-wayland-guard — broken symlink cleaned up.
3. local/recipes/AGENTS.md — catalog entry for redbear-wayland-guard was
wrong (claimed 'Rust' but the code was C LD_PRELOAD). Replaced with
REMOVED note explaining the policy violation and the correct fix
location in libwayland.
4. local/recipes/system/firmware-loader/source/src/main.rs — converted
9 .expect() calls in the daemon init path (Socket::create, scheme_root,
create_this_scheme_fd, syscall::call_wo notify, setrens, next_request,
write_response) to Result propagation. get_init_notify_fd() and
notify_scheme_ready() now return Result; run_daemon() returns Result and
main() matches on Err to log+exit(1) cleanly. The daemon was
crashing the entire firmware-delivery subsystem on any init failure;
now init can fall back or restart the daemon.
5. local/recipes/system/{redbear-keymapd,redbear-ime,redbear-accessibility}/
source/src/main.rs — three scheme daemons used the same
Socket::create().expect() + register_sync_scheme().expect() pattern.
Replaced all six .expect() calls with match expressions that
log_msg('ERROR', ...) and process::exit(1). Same pattern.
6. local/docs/NETWORKING-AND-DRIVERS-SYSTEMATIC-ASSESSMENT-2026-07-27.md —
struck through 5 references to the now-removed redbear-wayland-guard
(line 65 missing-daemons list, line 344 table row, line 397
implementation list, line 414 source-list, line 797 P3-8 backlog).
7. local/docs/SUPERSEDED-DOC-LOG.md — appended a 'Rounds 11-14 Source-Level
Supersessions' table logging every lie-grade fix and stale-doc
strike from this session. Mirrors the original deletion-log style for
consistency, and gives operators a single place to see what was
resolved and where. Documents the emerging pattern: lie-grade code in
Red Bear concentrates in (a) relibc panic-site catch-alls (addressed
rounds 9-10), (b) scheme daemon init paths using .expect() instead of
Result (rounds 11-14), (c) Mesa DRM/Wayland stubbing (rounds 12;
remaining work tracked in 3D-DESKTOP-COMPREHENSIVE-PLAN.md).
Not committed in this commit (operator's parallel work, to be
committed by them):
- driver-manager/* (N-tier edits)
- redbear-sessiond/manager.rs (can_* probe refinements)
- redbear-statusnotifierwatcher/* (recipe + source)
- redbear-dbus-services/* (dbus service cleanup)
- redox-driver-core/manager.rs (test-only)
- Mesa redox_drm_cs.c (CS submit fix)
7 files changed in this commit + 2 deletions.
Commit 222d5186eb ('add minimal # Safety comments to 70 files')
inserted a '// SAFETY: ...' line mid-token in backend.rs:1405,
splitting 'perms.set_mode(0o755);' into 'perms.set_mo' + comment +
'de(0o755);'. The result is a compilation error that prevents the
entire redbear-wifictl crate from building — including the new
dbus_nm.rs interface from e65a23fd6b.
Restore the single-line call. The Safety rationale is captured by
the surrounding cfg(unix) block.
Verified: cargo check --features dbus-nm compiles, 35 unit tests
+ 2 cli_transport pass.
The Round 11 commit (a9e1c34e27) fixed both findings 14/15 and
18/18b/19 in the assessment doc; the Round 11 fix and Round 12
follow-ups (this round) update the remaining stale references.
1. local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md §10 config table
(lines 1159-1160): marked wifi-experimental.toml and
bluetooth-experimental.toml include-typo as ✅ FIXED 2026-07-27
(was still listed as open).
2. local/docs/NETWORKING-AND-DRIVERS-CODE-ASSESSMENT-2026-07-27.md:
struck through:
- Finding 15 (redbear-passwd missing [source])
- Critical-path P0-12/13/14 (include typo + [source] todo)
- The Critical Path Hierarchy bullet list items
- TODO priority list line 718 (redbear-passwd [source])
- Backlog line 923 (C-23)
Marked each with ✅ RESOLVED 2026-07-27 (commit a9e1c34e27).
These were the last unstruck-through references after the
Round 11 fix landed. The assessment doc is now consistent
with the post-fix state.
2 files changed, +14/-12.
Submodule local/sources/base updated to c5b32f9f, which replaces
three production panic sites with proper error handling: vesad's
bare panic!() at loop exit, nvmed's timeout panic, and two
commented-out NVMe queue-error panics.
vasilito