summaryrefslogtreecommitdiff
path: root/9proc
Commit message (Collapse)AuthorAge
* README: a package that uses cloud9, as test/consumer doesHEADmainGabriel Schneider3 days
| | | | | | | | | | | | | | | | | | | The README and 9proc's told a consumer to pass .target and .optimize to b.dependency("cloud9", ...), and to swap the URL pin for a path while working on both packages. Now: the two modules take no options, and the whole build.zig of a program on cloud9 is written out (eleven lines, the form test/consumer uses); nothing else of cloud9's build runs in it. The sibling checkout is Zig's --fork=../cloud9, with the manifest untouched. Checked outside the tree: that build.zig, in a package pinning cloud9 by URL and hash (pardes's pin, 7f418a6b, from a copy of its zig-pkg entry), builds and runs; with --fork=<this checkout> it builds against this one ("fork ... matched 1 cloud9 packages", and no jj or date at configure); and against this tree as a fetched package (a tarball of its tracked files, so the manifest's paths filter applies) it builds too. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_016Y9MNBECMWcJD5pdS4SR6T
* build: a library's part for a consumer, and no moreGabriel Schneider3 days
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A package that depends on cloud9 ran all of its build(): the tests, 9web, the probes and the three program fragments, with the jj and the date 9proc's fragment spawns at configure, and it had to pass .target and .optimize, since the module carried both (one forgotten, cloud9 was Debug inside a release build). Now build() exports two modules with no target or optimize of their own, which take their importer's (std.Build.Module's CreateOptions: unspecified options are inherited): cloud9, and 9proc beside it at the top level, then returns when it is not the root (b.isRoot()). A consumer writes b.dependency("cloud9", .{}).module("cloud9"). The root's tests and programs root a compilation on the library, which needs a target, so they make their own module from the same file: the five lines the module took before, now a createModule, and 9proc's fragment makes its copy with createModule where it exported with addModule (no line more). The target and optimize options are still declared before the return: pardes and sketchbook pass both today, and an undeclared option a dependency is given is logged as "invalid option" (target, cpu and optimize) with a stack trace on every configure of theirs (not fatal: Build.dependencyResolved reports it, only the root's invalid options exit, compiler/configurer.zig:146-158; seen in a consumer: rc 0, three errors). The comment says to move both under the return once they pass nothing. zig build test 106 of 108 at load 15 (serve's "a ticket of a hung-up client" and "repeated connect/disconnect", the two known to fail under load; see the next change for quiet runs); install into a scratch prefix builds 9web, 9ns, 9agents, 9proc-demo and cloud9-probe as before. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_016Y9MNBECMWcJD5pdS4SR6T
* Build with Zig 0.17Gabriel Schneider2026-10-21
|
* 9proc: the test of a read past the parking cap expects the engine's "too ↵Gabriel Schneider2026-10-01
| | | | | | | | | | | | many reads waiting: N", as fs has refused it since 4af5c95 4af5c95 made the engine refuse a request it has no slot to park in with "too many reads waiting: N" instead of EAGAIN's C string; 9proc's test of its provider parking still expected the old words, so programs-test has failed since. It now names the engine's own refusal, Engine.e_waiting. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* 9ns --mntgen: registry subdirectories are mount points tooGabriel Schneider2026-09-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A registry entry that is a directory is now served the way the root is: a synthetic directory listing the real one, dialing the sockets inside it on walk and recursing into further directories, to max_synth_depth (8) levels across max_synth_dirs (64) synthetic nodes. That is the plan9port mntgen shape and the layout zmx now posts under, so a live session reads at /mnt/9p/zmx/<name>. Before this a directory in the registry was dialed like a socket and answered EIO for good. post gains the two entry points the traversal needs: postedDir (the registry scan, against any directory) and dialPath (a dial by composed path, no name validation). Hardening, each from an attack that broke the code: - BATCH_FORGET carries entries for many owners and puts 0 in the header nodeid, so routing it by the header dropped all of them: 32 of 64 synthetic slots leaked in one close burst and the subdirectories that held them answered EIO forever. distributeForgets unpacks the body and hands each entry to its owner. - probe() and connectBlocking() copied a caller's path into the kernel address with no bound: a path past sun_path overran the 110-byte stack sockaddr (a panic in Debug, silent corruption in ReleaseFast). Both refuse it now, probe as `.live` so a claim never deletes what it could not inspect. - That bound then caught 9proc's own listener, which handed probe() the whole 108-byte sun_path array instead of the path inside it. The probe reads `.live` for anything it cannot ask about, so every stale socket became AlreadyListening and no server could ever take a dead predecessor's name back. It passes the path now. Suites: 87/87 root (+7 post/serve attack regressions), 48/48 9ns, 51+88 9ns integration (+4 traversal and slot-recycling checks), 213/0 9ns adversarial, 60/60 9proc plus its adversarial suites with a new stale-socket takeover check, freestanding green.
* post registry + 9ns --mntgen: the /srv translationGabriel Schneider2026-09-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | cloud9.post: servers post their socket under a name in $XDG_RUNTIME_DIR/9p (post/unpost, posted, dial, Watch) and serve.Runner.listenPosted posts a server by name, unposting on stop. Names are budget-checked against the 108-byte socket path; a claim binds+listens at a private temp path and takes the name with atomic renames under flock (RENAME_NOREPLACE for free names, RENAME_EXCHANGE grab-verify-commit for stale ones): the registry path is never unlinked by a claim, live names refuse with AlreadyPosted, foreign files with NotSocket, and unpost removes only the caller's inode-matched entry. Watch surfaces inotify overflow and a replaced registry dir. 9ns --mntgen [--mount DIR] -- PROGRAM: one FUSE mount at /mnt/9p whose synthetic root lists the posted registry (no connection made); a walk into an unmounted name dials it and runs the existing bridge dispatch in a per-server worker thread, routed by mount index in the node id's top bits (ordinals never reused, cap 4096); a dead server answers EIO on its subtree and is re-dialed on the next walk. The dial watches stop_fd through Tversion (connectWatched). All existing 9ns forms are unchanged. 9proc's unix listener no longer blind-unlinks its path: a foreign non-socket is refused (Occupied), a live server is refused (AlreadyListening), only a refused socket is cleared, and stop() unlinks only the listener's own inode-matched socket. Hardened by adversarial review (GLM 5.3 x2 + DeepSeek V4.1 Flash, all high-thinking): double-bind races on one name (0 in 180k rounds), foreign-file TOCTOU deletions (0 in 4M flips), a 255-byte-name listing panic, inotify queue overflow silently dropped, listenPosted silently overwriting, dial-time Tversion hangs wedging the dispatcher, --debug silently ignored in mntgen, and xattr/statx probes answering EPERM on the synthetic root (broke `ls -l /mnt/9p`). Tests: root 80/80, 9ns 47/47, 9proc 60/60, integration 88/88 + mntgen 37/37, adversarial 213/0, freestanding riscv32 gate green.
* 9proc core becomes a backend of cloud9.fs; engine gains optional featuresGabriel Schneider2026-09-20
| | | | | | | | | | | | | | | | 9proc's own fid table, walk loop and dir-read engine are replaced by cloud9.fs.Server; the tree (static, vars, providers) is served through the engine's Req/Reply contract with node ids that keep the old qid scheme. Providers may answer later by returning error.Again (parked in the engine, retried each step, Tflush -> EINTR); no new files are exposed. Engine (backward compatible, all opt-in via Backend.features / Options): create, remove, wstat, reference accounting for backends that count handles, a salted fid index, name_capacity 0 (names from getattr), Reply.ename for backend-chosen error text, Attr.path/version/atime. Engine-level error strings and the 217-byte msize floor now apply to 9proc; tests updated accordingly. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* 9ns: --name and /mnt/9p/<name> mounts, qid.path as inode number, interrupts ↵Gabriel Schneider2026-09-19
| | | | | | | | | | | | | | | | | | | | as Tflush - --name NAME (default derived from the transport: socket basename, tcp-IP-PORT, spawned command, fdN) mounts at /mnt/9p/<name>; --mount still overrides. ensureMountpoint walks down and creates missing components, shadowing the deepest unwritable ancestor. NINE_MOUNT is the only exported variable. - The inode number reported to the kernel is the 9P qid.path for every node, root included; a server handing qid.path 1 to a file (Pardes /self) no longer collides with the root. - FUSE_INTERRUPT for the request in flight becomes Tflush; a blocked read returns EINTR when the server answers the flush, chunked transfers return short counts, other requests arriving meanwhile are stashed and served next. Servers ignoring Tflush still block until they answer. - 9ns-test now covers nine/bridge/fuse; new adv_bridge_interrupt suite (28); 9ns-itest grows to 88 checks. Co-Authored-By: Claude Fable 5.1 <[email protected]>
* Rename programs: 9player -> 9ns, introspect -> 9proc, app -> web (9web)Gabriel Schneider2026-09-19
Directories, binaries, build options (-D9ns, -D9proc), step names, module name (9proc), thread and fs names, env var NINEPLAYER_MOUNT -> NINE_MOUNT, docs and test scripts. Browser assets move to web/static. Co-Authored-By: Claude Fable 5.1 <[email protected]>