Skip to content

Zero token must not attach a fenced volume - #91

Merged
jaredLunde merged 3 commits into
beyondoss:mainfrom
paulocsanz:dst/b24-zero-token
Aug 15, 2026
Merged

Zero token must not attach a fenced volume#91
jaredLunde merged 3 commits into
beyondoss:mainfrom
paulocsanz:dst/b24-zero-token

Conversation

@paulocsanz

Copy link
Copy Markdown
Contributor

fence_attach(9, 4, 0, 0) Granted. attach_fence on the same composed tokens Rejects. The recovery model checks the pure rule; storage ran the wrapper. Combined with create stamping placement_generation = 0, the first attach is the bypass.

Two commits: a test that fails on main, then fence_attach is just attach_fence on the composed tokens. First attach against (0,0) still Grants (>=). A (0,0) caller against a volume that already holds a token Rejects.

git checkout HEAD~1 && cargo test --lib zero_token fails; HEAD passes.

fence_attach(9,4,0,0) is Grant today; attach_fence on the same tokens is Reject. First attach against (0,0) stays Grant. This fails on current main.
fence_attach now is attach_fence on the composed tokens. First attach (stored 0,0) still Grants. A zero token against a fenced volume Rejects.
API suite still expected the gen-0 bypass (201). Same machine as fence_attach: (0,0) against stored gen 9 is Reject.
@jaredLunde
jaredLunde merged commit f030d40 into beyondoss:main Aug 15, 2026
24 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants