[FEATURE] Preserve provider defaults in owned namespace CREATE #13

Open
opened 2026-10-19 00:30:10 +02:00 by erikinkinen · 5 comments
Owner

Problem and motivation

Owned namespace CREATE must preserve the selected filesystem's creation policy.
The current namespace request carries flags and a path, while the retained
provider creation interface requires explicit mode, owner, group and mask.
Hard-coding these in Vfsd would change configurable FAT catalog defaults.

Proposed behavior and scope

Add a distinct retained provider operation for creating a regular file with that
provider's existing administrative defaults. Its request retains the original
root, acquisition key, parent, fresh permission revision, descriptor access,
optional timestamp and final component. It carries no caller-selected ownership
or permission metadata. The provider selects its established defaults inside the
same exclusive creation turn and reuses its existing conditional creation and
original-key retirement machinery.

Coordinate LibIPC, the Vfsd provider adapter, and Ramfsd, E2fsd and Fatd before
adoption. The namespace Acquire format and explicit-metadata creation operation
remain unchanged. This operation does not introduce socket creation or replace
process-mediated POSIX creation policy.

Authority, security and reliability

The existing native provider route and retained root remain the authority
ceiling. Original parent identity, revision, writable admission and complete
response storage are checked before effects. Reserve the original acquisition
key and disposal custody first. Preserve exact request/opcode correlation,
partial failures, reply loss, cancellation and first-error precedence. A native
completion alone never establishes provider disposal. No unowned legacy CREATE
fallback, new grant or caller-selected UID/GID/mode is permitted.

Acceptance criteria

  • Document the request/result layout, regular-file access domain and rollout.
  • Add literal codec controls for exact framing, opcode, keys, reserved bytes,
    malformed access, short storage and response correlation.
  • Ramfsd and E2fsd preserve their existing file mode, owner and group.
  • Fatd uses the actual mounted catalog's configurable mode, owner and group,
    including nondefault values, without deriving policy from parent metadata.
  • Preserve fresh parent checks, read-only denial, original-key replay fencing,
    handle exhaustion, uncertain completion and positive retirement controls.
  • Vfsd uses the retained operation and original acquisition custody without
    widening namespace flags or exposing arbitrary creation metadata.
  • Publish coherent catalogs, component documentation and the technical manual;
    complete strict builds, tests and relevant native integration scenarios.

Alternatives and tradeoffs

Sending explicit metadata from namespace clients would change their policy
surface. Copying parent metadata would not preserve provider defaults. Querying
creation policy separately would add another exchange and a freshness boundary.
A distinct provider operation keeps policy selection beside the existing
exclusive mutation while preserving the explicit POSIX interface.

Tracking and rollout

This completes CREATE parity within the owned namespace lifetime migration.
Publish the shared codec and provider implementations before Vfsd adoption, then
select the matching graph in Integration. Keep the existing operation available
for its explicit process-policy consumers.

## Problem and motivation Owned namespace CREATE must preserve the selected filesystem's creation policy. The current namespace request carries flags and a path, while the retained provider creation interface requires explicit mode, owner, group and mask. Hard-coding these in Vfsd would change configurable FAT catalog defaults. ## Proposed behavior and scope Add a distinct retained provider operation for creating a regular file with that provider's existing administrative defaults. Its request retains the original root, acquisition key, parent, fresh permission revision, descriptor access, optional timestamp and final component. It carries no caller-selected ownership or permission metadata. The provider selects its established defaults inside the same exclusive creation turn and reuses its existing conditional creation and original-key retirement machinery. Coordinate LibIPC, the Vfsd provider adapter, and Ramfsd, E2fsd and Fatd before adoption. The namespace Acquire format and explicit-metadata creation operation remain unchanged. This operation does not introduce socket creation or replace process-mediated POSIX creation policy. ## Authority, security and reliability The existing native provider route and retained root remain the authority ceiling. Original parent identity, revision, writable admission and complete response storage are checked before effects. Reserve the original acquisition key and disposal custody first. Preserve exact request/opcode correlation, partial failures, reply loss, cancellation and first-error precedence. A native completion alone never establishes provider disposal. No unowned legacy CREATE fallback, new grant or caller-selected UID/GID/mode is permitted. ## Acceptance criteria - [x] Document the request/result layout, regular-file access domain and rollout. - [x] Add literal codec controls for exact framing, opcode, keys, reserved bytes, malformed access, short storage and response correlation. - [x] Ramfsd and E2fsd preserve their existing file mode, owner and group. - [x] Fatd uses the actual mounted catalog's configurable mode, owner and group, including nondefault values, without deriving policy from parent metadata. - [ ] Preserve fresh parent checks, read-only denial, original-key replay fencing, handle exhaustion, uncertain completion and positive retirement controls. - [x] Vfsd uses the retained operation and original acquisition custody without widening namespace flags or exposing arbitrary creation metadata. - [ ] Publish coherent catalogs, component documentation and the technical manual; complete strict builds, tests and relevant native integration scenarios. ## Alternatives and tradeoffs Sending explicit metadata from namespace clients would change their policy surface. Copying parent metadata would not preserve provider defaults. Querying creation policy separately would add another exchange and a freshness boundary. A distinct provider operation keeps policy selection beside the existing exclusive mutation while preserving the explicit POSIX interface. ## Tracking and rollout This completes CREATE parity within [the owned namespace lifetime migration](https://git.erikinkinen.fi/erix/lib-ipc/issues/12). Publish the shared codec and provider implementations before Vfsd adoption, then select the matching graph in Integration. Keep the existing operation available for its explicit process-policy consumers.
Author
Owner

LibIPC 9e32c52 publishes the distinct provider-default request and response with literal framing and correlation controls. UID, GID, mode and mask stay out of the request; the original provider chooses its defaults. The Vfsd and filesystem adapters are being completed next.

[LibIPC 9e32c52](https://git.erikinkinen.fi/erix/lib-ipc/commit/9e32c525f13c1c3a15cd36dcb8e2b6e77f091a7a) publishes the distinct provider-default request and response with literal framing and correlation controls. UID, GID, mode and mask stay out of the request; the original provider chooses its defaults. The Vfsd and filesystem adapters are being completed next.
Author
Owner

Ramfsd d0a292c now implements the memory provider adapter using its established administrative defaults. E2fsd, Fatd and Vfsd remain in progress. The shared provider criterion stays open until all three filesystem adapters are complete.

[Ramfsd d0a292c](https://git.erikinkinen.fi/erix/ramfsd/commit/d0a292c018b10ad222d836e6619a2452c18d824c) now implements the memory provider adapter using its established administrative defaults. E2fsd, Fatd and Vfsd remain in progress. The shared provider criterion stays open until all three filesystem adapters are complete.
Author
Owner

Fatd 9753c56 completes the FAT/exFAT adapter alongside the published memory adapter. Administrative defaults come from the actual catalog header. E2fsd and the Vfsd caller remain in progress, so the shared provider criterion stays open.

[Fatd 9753c56](https://git.erikinkinen.fi/erix/fatd/commit/9753c562e3171bb92b771e3236cd1dfa874bb602) completes the FAT/exFAT adapter alongside the published memory adapter. Administrative defaults come from the actual catalog header. E2fsd and the Vfsd caller remain in progress, so the shared provider criterion stays open.
Author
Owner

The provider implementations are now published: Ramfsd d0a292c, E2fsd 053db7f, and Fatd 9753c56. Memory and ext2 preserve their existing administrative policy; FAT/exFAT uses the actual catalog defaults. The two provider-specific checklist items are complete. Vfsd adoption, catalog coordination, and native lifecycle coverage remain open.

The provider implementations are now published: [Ramfsd d0a292c](https://git.erikinkinen.fi/erix/ramfsd/commit/d0a292c018b10ad222d836e6619a2452c18d824c), [E2fsd 053db7f](https://git.erikinkinen.fi/erix/e2fsd/commit/053db7f3780c4e0f485a905d537c442ab5bb3bcd), and [Fatd 9753c56](https://git.erikinkinen.fi/erix/fatd/commit/9753c562e3171bb92b771e3236cd1dfa874bb602). Memory and ext2 preserve their existing administrative policy; FAT/exFAT uses the actual catalog defaults. The two provider-specific checklist items are complete. Vfsd adoption, catalog coordination, and native lifecycle coverage remain open.
Author
Owner

Vfsd adoption is published at dae0e1f4, so that criterion is checked. CREATE uses the retained provider operation and original acquisition custody, with no caller-selected ownership or permission metadata. The coordinated catalogs and complete native lifecycle coverage remain open.

Vfsd adoption is published at `dae0e1f4`, so that criterion is checked. CREATE uses the retained provider operation and original acquisition custody, with no caller-selected ownership or permission metadata. The coordinated catalogs and complete native lifecycle coverage remain open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:47 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/lib-ipc#13
No description provided.