tests: record AFP open file fork write smoke success

This commit is contained in:
Mario Fetka
2026-05-30 21:21:35 +00:00
parent 9c1787345d
commit 2b614af27b

View File

@@ -1086,3 +1086,30 @@ Runtime status: the Create Date/Time smoke run is verified with `failures=0`.
The report showed `bitmap=0x0800`, `create=0x576e`, and the backing xattr
`user.org.mars-nwe.netware.fileinfo=0x01036e57aab90000000000000000` after
setting epoch `1700000000`.
## AFP Open File Fork write smoke success
AFP Open File Fork now routes data-fork write opens through the existing
NetWare open/share path instead of rejecting write access at the AFP wrapper
layer.
Verified smoke run:
```text
AFP Open File Fork write create file
AFP Create File subfunction=0x02 path=SYS:PUBLIC/atst2 parent=SYS:PUBLIC leaf=atst2 parent_entry_id=0x00000004 entry_id=0x1a81505a verified
AFP Open File Fork write access
AFP Open File Fork path=SYS:PUBLIC/atst2 handle=1 fork=0 access=0x02 fork_len=0
AFP Open File Fork write cleanup
AFP Delete path=SYS:PUBLIC/atst2 parent=SYS:PUBLIC leaf=atst2 parent_entry_id=0x00000004 verified
AFP Open File Fork resource fork rejected
AFP Open File Fork returned expected completion 0x9c: path=SYS:PUBLIC/pmdflts.ini fork=1 access=0x01
Summary: failures=0
```
The positive write-open smoke only covers the AFP data fork. AFP resource
fork opens are still intentionally rejected with completion 0x9c.