Skip to content

0.2.0: the kernel's refusal of a start for its size is kal_err_no_space (openkal 0.26) - #5

Open
Sunrisepeak wants to merge 2 commits into
mainfrom
openkal-0.26.0
Open

Sunrisepeak wants to merge 2 commits into
mainfrom
openkal-0.26.0

Conversation

@Sunrisepeak

@Sunrisepeak Sunrisepeak commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

openkal 0.26.0 (mcpplibs/openkal#69) requires of every implementation that a start be bounded by the environment alone (clause 7.6) and that observable units be claimed only where a reference can be made (clause 7.18). This is openkal-freebsd's release for it.

What changes

  • src/common.h, src/sys.h: E2BIG is kal_err_no_space. It was not named in okf::translate and fell to kal_err_io. fexecve answers it when the arguments and the environment exceed ARG_MAX; the copy reports the error number through the report pipe and the starter translates it.
  • mcpp.toml: version 0.2.0, openkal = "^0.26.0".
  • README.md, CHANGELOG.md: the section for 0.2.

What does not change, and why

  • No count bound existed. kal_process_spawn allocates both vectors at their measured size (argc + 1, envc + inherited + 2 slots), and kal_env_arg* / kal_env_var* read the vectors the kernel gave the program where they lie (src/core.cpp, src/start.cpp); there is no table on either side.
  • Clause 7.18. kal_process_props does not state KAL_PROCESS_PROP_JOB_OBSERVE and kal_process_job_create answers kal_err_not_supported, which is what 0.26 requires of an implementation that does not claim the property.

What was measured

  • Locally, tools/check-standalone.sh with clang++ 23.1.3 on a Linux host: every source compiles for x86_64 and aarch64 without a system header. Nothing was run on FreeBSD locally.
  • In this pull request's CI, the hosted arrangement on FreeBSD 15.1 (amd64 and arm64), the specification at openkal-0.26.0: 326 observations held, 0 did not hold, 13 not observed (main, with openkal 0.25.3's suite: 322 held). The four observations of 0.26 are the difference and all hold: 2,000 arguments, 2,000 variables, an argument of 1 MiB, and "an implementation that does not claim observable units refuses to declare one".

Expected to wait (the platform release)

Both standalone conformance jobs build for <arch>-freebsd-musl through the engine's default platform and are refused:

error: openkal is requested as '^0.26.0' by mcpplibs.openkal-freebsd@path, and the platform openkal-platform 0.27.1 is a version group that names openkal 0.25.0.

They hold once the platform is released for openkal 0.26.

Not verified

  • Which of the three starts the kernel admitted and which it refused is not in the suite's output; the suite holds on either. With E2BIG untranslated the refusal would not have held.
  • The standalone arrangement was compiled and not run.

…ce (openkal 0.26)

- E2BIG from fexecve is kal_err_no_space, where it was kal_err_io (clause 7.6);
  no bound of this implementation's own existed upon an argument vector or an
  environment
- observable units remain unclaimed and kal_process_job_create answers
  kal_err_not_supported (clause 7.18)
- openkal ^0.26.0
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