Daniel Samson
1b1c587c14
Three services had each written the same thing and got it three different ways: input polled the process list to notice a dead subscriber, and only when someone else subscribed; the power service never noticed at all; the device manager noticed drivers but not subscribers. The harness owns the table now, driven by the events a protocol declares — it registers on the reserved verb, frames each event once, posts to everyone interested without waiting on any of them, and reclaims a slot when the kernel says its owner died. Interest masks moved to the envelope, so a subscriber that wants only mice asks the same way everywhere. Two consequences the plan had not foreseen. The device manager now hears a supervised child's death twice, once as its supervisor and once as a subscriber, so restart backoff counted every crash twice and gave up after half as many; it retires the id before counting. And the kernel's published exit table had eight slots for what is now six subscriptions in a plain boot, so it holds sixteen. The other half is a hole the design named early and left standing: a backend handed out a small integer and then honoured it from anyone. A process that guessed a file's node id read another client's file; a display layer had no owner at all, so any client could reconfigure or destroy any layer; a USB device token was never checked against the client that opened it. Each is now bound to the task that opened it, and a wrong owner gets exactly what an unknown id gets — the refusal must not become the oracle the identical answers elsewhere were designed to remove. Closing a file changed with it: it used to succeed unconditionally, which would have told a caller which ids existed. Suite 111/111, with a new case in which one process holds a file and a layer, hands both ids to a second process, and finds them untouched after that process has tried everything with them.
122 lines
7.6 KiB
Zig
122 lines
7.6 KiB
Zig
.{
|
|
// This is the default name used by packages depending on this one. For
|
|
// example, when a user runs `zig fetch --save <url>`, this field is used
|
|
// as the key in the `dependencies` table. Although the user can choose a
|
|
// different name, most users will stick with this provided value.
|
|
//
|
|
// It is redundant to include "zig" in this name because it is already
|
|
// within the Zig package namespace.
|
|
.name = .danos,
|
|
// This is a [Semantic Version](https://semver.org/).
|
|
// In a future version of Zig it will be used for package deduplication.
|
|
.version = "0.0.0",
|
|
// Together with name, this represents a globally unique package
|
|
// identifier. This field is generated by the Zig toolchain when the
|
|
// package is first created, and then *never changes*. This allows
|
|
// unambiguous detection of one package being an updated version of
|
|
// another.
|
|
//
|
|
// When forking a Zig project, this id should be regenerated (delete the
|
|
// field and run `zig build`) if the upstream project is still maintained.
|
|
// Otherwise, the fork is *hostile*, attempting to take control over the
|
|
// original project's identity. Thus it is recommended to leave the comment
|
|
// on the following line intact, so that it shows up in code reviews that
|
|
// modify the field.
|
|
.fingerprint = 0x402a07325b01d626, // Changing this has security and trust implications.
|
|
// Tracks the earliest Zig version that the package considers to be a
|
|
// supported use case.
|
|
.minimum_zig_version = "0.16.0",
|
|
// This field is optional.
|
|
// Each dependency must either provide a `url` and `hash`, or a `path`.
|
|
// `zig build --fetch` can be used to fetch all dependencies of a package, recursively.
|
|
// Once all dependencies are fetched, `zig build` no longer requires
|
|
// internet connectivity.
|
|
.dependencies = .{
|
|
// The danos build API — the shared user-binary recipe every build file
|
|
// (root and per-binary packages) consumes (docs/build-packages-plan.md).
|
|
.@"build-support" = .{ .path = "build-support" },
|
|
// The library domains, each a package exporting its modules.
|
|
.kernel = .{ .path = "library/kernel" },
|
|
.device = .{ .path = "library/device" },
|
|
.client = .{ .path = "library/client" },
|
|
.protocol = .{ .path = "library/protocol" },
|
|
.csv = .{ .path = "library/csv" },
|
|
.@"xkeyboard-config" = .{ .path = "library/xkeyboard-config" },
|
|
// Binary packages (phase 2), consumed as artifacts for the boot image.
|
|
.@"pci-bus" = .{ .path = "system/drivers/pci-bus" },
|
|
.init = .{ .path = "system/services/init" },
|
|
.fat = .{ .path = "system/services/fat" },
|
|
.display = .{ .path = "system/services/display" },
|
|
.@"display-demo" = .{ .path = "system/services/display-demo" },
|
|
.@"device-manager" = .{ .path = "system/services/device-manager" },
|
|
.input = .{ .path = "system/services/input" },
|
|
.logger = .{ .path = "system/services/logger" },
|
|
// The discovery pair and the /test fixtures are lazy: only what a
|
|
// given build actually ships gets its build file loaded and compiled
|
|
// (-Ddiscovery picks one of the pair; -Dtest-case pulls the fixtures).
|
|
.acpi = .{ .path = "system/services/acpi", .lazy = true },
|
|
.fdt = .{ .path = "system/services/fdt", .lazy = true },
|
|
.@"ps2-bus" = .{ .path = "system/drivers/ps2-bus" },
|
|
.@"usb-xhci-bus" = .{ .path = "system/drivers/usb-xhci-bus" },
|
|
.@"usb-hid" = .{ .path = "system/drivers/usb-hid" },
|
|
.@"usb-storage" = .{ .path = "system/drivers/usb-storage" },
|
|
.@"virtio-gpu" = .{ .path = "system/drivers/virtio-gpu" },
|
|
.@"vfs-test" = .{ .path = "test/system/services/vfs-test", .lazy = true },
|
|
.@"fat-test" = .{ .path = "test/system/services/fat-test", .lazy = true },
|
|
.@"badge-scope-test" = .{ .path = "test/system/services/badge-scope-test", .lazy = true },
|
|
.@"shared-memory-server" = .{ .path = "test/system/services/shared-memory-server", .lazy = true },
|
|
.@"shared-memory-client" = .{ .path = "test/system/services/shared-memory-client", .lazy = true },
|
|
.@"crash-test" = .{ .path = "test/system/services/crash-test", .lazy = true },
|
|
.@"device-list" = .{ .path = "test/system/services/device-list", .lazy = true },
|
|
.@"pci-cap-test" = .{ .path = "test/system/services/pci-cap-test", .lazy = true },
|
|
.@"iommu-fault-test" = .{ .path = "test/system/services/iommu-fault-test", .lazy = true },
|
|
.@"input-source" = .{ .path = "test/system/services/input-source", .lazy = true },
|
|
.@"input-test" = .{ .path = "test/system/services/input-test", .lazy = true },
|
|
.@"args-echo" = .{ .path = "test/system/services/args-echo", .lazy = true },
|
|
.@"process-test" = .{ .path = "test/system/services/process-test", .lazy = true },
|
|
.@"thread-test" = .{ .path = "test/system/services/thread-test", .lazy = true },
|
|
.@"user-memory-test" = .{ .path = "test/system/services/user-memory-test", .lazy = true },
|
|
.@"protocol-registry-test" = .{ .path = "test/system/services/protocol-registry-test", .lazy = true },
|
|
.@"protocol-denied-test" = .{ .path = "test/system/services/protocol-denied-test", .lazy = true },
|
|
.@"protocol-conformance-test" = .{ .path = "test/system/services/protocol-conformance-test", .lazy = true },
|
|
// See `zig fetch --save <url>` for a command-line interface for adding dependencies.
|
|
//.example = .{
|
|
// // When updating this field to a new URL, be sure to delete the corresponding
|
|
// // `hash`, otherwise you are communicating that you expect to find the old hash at
|
|
// // the new URL. If the contents of a URL change this will result in a hash mismatch
|
|
// // which will prevent zig from using it.
|
|
// .url = "https://example.com/foo.tar.gz",
|
|
//
|
|
// // This is computed from the file contents of the directory of files that is
|
|
// // obtained after fetching `url` and applying the inclusion rules given by
|
|
// // `paths`.
|
|
// //
|
|
// // This field is the source of truth; packages do not come from a `url`; they
|
|
// // come from a `hash`. `url` is just one of many possible mirrors for how to
|
|
// // obtain a package matching this `hash`.
|
|
// //
|
|
// // Uses the [multihash](https://multiformats.io/multihash/) format.
|
|
// .hash = "...",
|
|
//
|
|
// // When this is provided, the package is found in a directory relative to the
|
|
// // build root. In this case the package's hash is irrelevant and therefore not
|
|
// // computed. This field and `url` are mutually exclusive.
|
|
// .path = "foo",
|
|
//
|
|
// // When this is set to `true`, a package is declared to be lazily
|
|
// // fetched. This makes the dependency only get fetched if it is
|
|
// // actually used.
|
|
// .lazy = false,
|
|
//},
|
|
},
|
|
// Specifies the set of files and directories that are included in this package.
|
|
// Only files and directories listed here are included in the `hash` that
|
|
// is computed for this package. Only files listed here will remain on disk
|
|
// when using the zig package manager. As a rule of thumb, one should list
|
|
// files required for compilation plus any license(s).
|
|
// Paths are relative to the build root. Use the empty string (`""`) to refer to
|
|
// the build root itself.
|
|
// A directory listed here means that all files within, recursively, are included.
|
|
.paths = .{""},
|
|
}
|