@ai-ecoverse/slicc-kernel 1.60.1 → 1.60.2

package/README.md

@@ -384,7 +384,7 @@ The proxy answers `200` with `Content-Type: application/vnd.slicc.raw-fetch`: a
 
 ## Filesystem
 
-`/` is the OPFS root. Each process mounts the top-level directories that exist when it starts (plus `/usr` and `/bin`), so files in them are shared by all processes and visible through the OPFS API as soon as the process that wrote them has closed them; `run` resolves only after that. `createKernel` creates `/tmp` and `/home` in OPFS, so they are shared too. Files directly in `/`, and directories created there after a process started, are OPFS as well, the same for Emscripten and WASI programs; only `/dev` and `/proc` live in each process's memory. An OPFS or IndexedDB failure that has no POSIX counterpart is `EIO`; its message names the DOM error and the operation (`lookup`, `read`, `write`, `commit` or `sidecar`), and the kernel worker logs the first of each kind to its console. File contents are buffered per open file and written back on close, `fsync` and exit; metadata operations (`mkdir`, `rename`, `rm`, …) go straight to OPFS. The kernel worker is the only writer.
+`/` is the OPFS root. Each process mounts the top-level directories that exist when it starts (plus `/usr` and `/bin`), so files in them are shared by all processes and visible through the OPFS API as soon as the process that wrote them has closed them; `run` resolves only after that. `createKernel` creates `/tmp` and `/home` in OPFS, so they are shared too. Files directly in `/`, and directories created there after a process started, are OPFS as well, the same for Emscripten and WASI programs; only `/dev` and `/proc` live in each process's memory. A program's `mkdir` (WASI `path_create_directory`, Emscripten's `mkdir`) is exclusive, as on Linux: it fails with `EEXIST` when the name exists, and of several processes or threads making one name at once exactly one succeeds, so a directory works as a lock. Unlike Linux, a WASI program's `mkdir` under a missing directory makes the missing parents rather than failing with `ENOENT` (#380); a JS program's `ctx.fs.mkdir` makes parents too. An OPFS or IndexedDB failure that has no POSIX counterpart is `EIO`; its message names the DOM error and the operation (`lookup`, `read`, `write`, `commit` or `sidecar`), and the kernel worker logs the first of each kind to its console. File contents are buffered per open file and written back on close, `fsync` and exit; metadata operations (`mkdir`, `rename`, `rm`, …) go straight to OPFS. The kernel worker is the only writer.
 
 Directories are renamed with `FileSystemHandle.move()` where available, else by copy and delete.
 

package/dist/kernel-worker.js

@@ -7809,6 +7809,19 @@ function mkdirOptions(entry, mode = 511) {
   const parents = 511 & ~(entry.umask?.() ?? 18) | 192;
   return { recursive: true, owner: { ...owner, parents } };
 }
+async function mkdirExclusive(entry, path, mode) {
+  const { fs } = entry;
+  const { owner } = mkdirOptions(entry, mode);
+  const own = owner ? { owner } : {};
+  try {
+    await fs.mkdir(path, own);
+  } catch (err) {
+    if (err?.code !== "ENOENT") throw err;
+    const above = owner ? { owner: { ...owner, mode: owner.parents } } : {};
+    await fs.mkdir(path.slice(0, path.lastIndexOf("/")) || "/", { recursive: true, ...above });
+    await fs.mkdir(path, own);
+  }
+}
 async function chown(entry, path, req) {
   const cred = entry.cred?.();
   if (!cred) {
@@ -7841,7 +7854,7 @@ async function run(entry, path, req) {
     case "readdir-stat":
       return json2(await readdirStat(fs, path));
     case "mkdir":
-      await fs.mkdir(path, mkdirOptions(entry, req.mode));
+      await (req.exclusive ? mkdirExclusive(entry, path, req.mode) : fs.mkdir(path, mkdirOptions(entry, req.mode)));
       return done;
     case "rm":
       await fs.rm(path, { recursive: true });