Skip to content

wasm: execute late initcalls - #43

Merged
tombl merged 1 commit into
wasmfrom
wasm-late-initcalls
Aug 8, 2026
Merged

wasm: execute late initcalls#43
tombl merged 1 commit into
wasmfrom
wasm-late-initcalls

Conversation

@tombl

@tombl tombl commented Aug 8, 2026

Copy link
Copy Markdown
Owner

CONFIG_WASM keeps separate start and end arrays with one entry for each initcall level. Unlike the generic boundary table, these arrays have no trailing sentinel, but do_initcalls() still subtracted one from the number of levels. As a result, wasm skipped every normal and synchronous level-7 late initcall.

Iterate all eight named wasm initcall levels. Early, rootfs, and console initcalls keep their existing separate handling.

Validated with one-, three-, four-, and eight-CPU boots and the runner lifecycle suite.

Agent-Session: codex:019fe115-244a-76c1-b716-b8af6827da00

CONFIG_WASM keeps separate start and end arrays with one entry for each initcall level. Unlike the generic boundary table, these arrays have no trailing sentinel, but do_initcalls() still subtracted one from the number of levels. As a result, wasm skipped every normal and synchronous level-7 late initcall.

Iterate all eight named wasm initcall levels. Early, rootfs, and console initcalls keep their existing separate handling.

Validated with one-, three-, four-, and eight-CPU boots and the runner lifecycle suite.

Agent-Session: codex:019fe115-244a-76c1-b716-b8af6827da00
@tombl
tombl marked this pull request as ready for review August 8, 2026 14:08
@tombl
tombl merged commit 6dcb57e into wasm Aug 8, 2026
1 check passed
@tombl
tombl deleted the wasm-late-initcalls branch August 8, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant