@ai-ecoverse/slicc-kernel 1.143.4 → 1.143.5

package/README.md

@@ -910,13 +910,13 @@ A process's working directory is the directory it changed into, not just its pat
   - its relative lookups and creates are `ENOENT`;
   - `..` still reaches the parent.
   - an Emscripten program (bash, coreutils, …) and its forked subshells and children: relative paths resolve against `<path> (deleted)`, so `ls` fails with `cannot open directory '.'`, a glob matches nothing, and a relative create is `ENOENT`. `getcwd` is `ENOENT`, as on Linux, so a shell started there says `shell-init: error retrieving current directory` and its `pwd` fails, while bash's own `$PWD`, `cd ..` and `cd /abs` keep working.
-  - a JS program: `ctx.fs` and `ctx.sync.fs` with relative paths are `ENOENT`, and `../x` reaches the parent. `ctx.cwd` (and `process.cwd()`) keeps the plain path, as a WASIX program's `getcwd` does. This needs the sync lane, which JS programs have where `SharedArrayBuffer` is available.
+  - a JS program: `ctx.fs` and `ctx.sync.fs` with relative paths are `ENOENT`, and `../x` reaches the parent. `ctx.cwd` (and `process.cwd()`) keeps the plain path, as an older WASIX program's `getcwd` does. This needs the sync lane, which JS programs have where `SharedArrayBuffer` is available.
 - **Detection costs nothing in the steady state:**
   - each held directory has a counter in memory the kernel shares with the process. It moves only when this kernel, another tab, or a `postFsNotice` reports a change at that directory or above it: the kernel's own watcher paths, and every path and tree of a peer change or notice.
   - a process checks the counter, a memory read, before each relative lookup. Only after it moved does it ask the kernel once (`cwd-check`), and the kernel compares the inode at the path with the one it recorded.
 - **The `rm` record:** so that `rm -r d; mkdir d` can be told apart, removing a directory leaves the same small record a rename leaves at the name it vacates (see [Metadata](#metadata)).
 - **Limits:**
-  - a WASIX program's C library keeps the working directory as a string and turns relative paths into absolute ones before they reach the kernel. So a WASIX program still sees the new directory through relative paths, and `getcwd` still returns the path, until wasix-sysroot resolves relative paths against the working directory's descriptor ([#1164](https://github.com/ai-ecoverse/slicc-kernel/issues/1164) stays open for that).
+  - a WASIX program built on wasix-sysroot 2025.9.30-41 or later (its `slicc.libc` marker) resolves relative paths, and `*at(AT_FDCWD)`, against the working directory's descriptor, as a WASI program does: listing `.`, a relative create and a `stat` are `ENOENT`, `getcwd` is `ENOENT` as on Linux, and `chdir("..")` reaches the parent ([#1227](https://github.com/ai-ecoverse/slicc-kernel/issues/1227)). An older libc keeps the working directory as a string and turns relative paths into absolute ones before they reach the kernel, so it still sees the new directory through relative paths, and its `getcwd` keeps returning the path, since it builds a relative `chdir("..")` from it.
   - a removal between the check and the lookup is a race, as with any path, and the lookup sees the new directory.
   - on a `hostfs` folder the inode is the host's, which a host file system may reuse for the new directory (ext4 can; APFS doesn't). There the replacement isn't noticed.
   - with more than 1023 distinct working directories held at once, the rest are not tracked.

package/dist/kernel-worker.js

@@ -7598,7 +7598,7 @@ function satisfies(version, range2) {
 }
 
 // src/version.ts
-var KERNEL_VERSION = true ? "1.143.4" : "0.0.0-dev";
+var KERNEL_VERSION = true ? "1.143.5" : "0.0.0-dev";
 var OS_RELEASE = "6.0.0-slicc";
 function procVersion() {
   return `Linux version ${OS_RELEASE} (slicc-kernel ${KERNEL_VERSION}) #1 SMP PREEMPT_DYNAMIC

package/dist/node-process-worker.js

@@ -4976,6 +4976,7 @@ var init_wasi_host = __esm({
       startCwd;
       interruptWakes = false;
       strictEpoll = false;
+      cwdFd = false;
       entered = false;
       enteredSignals = 0;
       raisedOnEntry;
@@ -6725,7 +6726,7 @@ var KERNEL_VERSION, OS_RELEASE;
 var init_version = __esm({
   "src/version.ts"() {
     "use strict";
-    KERNEL_VERSION = true ? "1.143.4" : "0.0.0-dev";
+    KERNEL_VERSION = true ? "1.143.5" : "0.0.0-dev";
     OS_RELEASE = "6.0.0-slicc";
   }
 });
@@ -17317,7 +17318,7 @@ function posixSignal(sig) {
 function nsToMs(ns) {
   return Math.ceil(Number(ns) / 1e6);
 }
-var FDFLAGSEXT_CLOEXEC, SPAWN_OP_SIZE, SPAWN_OPS, RIGHTS_FD_WRITE, ICANON2, ECHO2, FUTEX_SLICE_MS, EINTR_LIBC, STRICT_EPOLL_LIBC, MAIN_HANDLE, WasixHost;
+var FDFLAGSEXT_CLOEXEC, SPAWN_OP_SIZE, SPAWN_OPS, RIGHTS_FD_WRITE, ICANON2, ECHO2, FUTEX_SLICE_MS, EINTR_LIBC, STRICT_EPOLL_LIBC, CWD_FD_LIBC, MAIN_HANDLE, WasixHost;
 var init_wasix_host = __esm({
   "src/process/wasi/wasix-host.ts"() {
     "use strict";
@@ -17342,6 +17343,7 @@ var init_wasix_host = __esm({
     FUTEX_SLICE_MS = 50;
     EINTR_LIBC = 22;
     STRICT_EPOLL_LIBC = 29;
+    CWD_FD_LIBC = 41;
     MAIN_HANDLE = 2147483647;
     WasixHost = class _WasixHost {
       process;
@@ -17360,7 +17362,9 @@ var init_wasix_host = __esm({
           driver,
           () => (this.threads?.tid ?? MAIN_TID) !== MAIN_TID
         );
-        if (module) host.strictEpoll = (libcVersion(module) ?? 0) >= STRICT_EPOLL_LIBC;
+        const libc = module ? libcVersion(module) ?? 0 : void 0;
+        if (libc !== void 0) host.strictEpoll = libc >= STRICT_EPOLL_LIBC;
+        if (libc !== void 0) host.cwdFd = libc >= CWD_FD_LIBC;
         if (module && !WebAssembly.Module.imports(module).some((i) => i.name === "fd_fdflags_set")) {
           host.fds.implicitCloexec = true;
           host.interruptWakes = (libcVersion(module) ?? 0) < EINTR_LIBC;
@@ -17500,6 +17504,7 @@ var init_wasix_host = __esm({
             mem.view().setUint32(out, host.o.parent?.() ?? host.o.ppid ?? 1, true);
           },
           getcwd: (buf, lenPtr) => {
+            if (host.cwdFd && host.fds.held && !host.fds.held.alive()) return E.NOENT;
             const bytes = new TextEncoder().encode(host.cwd);
             const max = mem.view().getUint32(lenPtr, true);
             mem.view().setUint32(lenPtr, bytes.length, true);