mars_nwe/mars-nwe
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases 2 Wiki Activity

tests: record AFP open file fork entry-id smoke success
All checks were successful
Source release / source-package (push) Successful in 51s
Details

Browse Source
This commit is contained in:
a
2026-05-30 21:44:21 +00:00
committed by Mario Fetka
parent 362a5779cb
commit 8e95b56ca6
1 changed files with 29 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
tests/linux/README.md
View File

@@ -1120,3 +1120,32 @@ 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.
## AFP Open File Fork entry-id smoke success
AFP Open File Fork now accepts entry-id-only data-fork opens for regular files
whose AFP ID is present in the nwatalk AFP entry-id metadata. The server
reverse-resolves file AFP IDs through the AFP/nwatalk metadata cache instead of
using DOS namespace directory numbers, then opens the resolved file through the
same NetWare open/share path used by path-backed AFP Open File Fork.
Verified smoke run after the WebSDK Get Entry ID From Path Name helper-layout
fix:
```text
AFP Open File Fork by Entry ID
AFP Open File Fork path=SYS:PUBLIC/pmdflts.ini entry_id=0x59f0e25b handle=1 fork=0 access=0x01 fork_len=8161 entry-id-only
AFP Open File Fork write access by Entry ID
AFP Open File Fork path=SYS:PUBLIC/atst2 entry_id=0x262fd43e handle=1 fork=0 access=0x02 fork_len=0 entry-id-only
AFP Open File Fork resource fork rejected
AFP Open File Fork returned expected completion 0x9c: path=SYS:PUBLIC/pmdflts.ini entry_id=0x00000000 fork=1 access=0x01
Summary: failures=0
```
This keeps the current policy split intact: directory Entry IDs may use the
existing namespace/basehandle mapping, while regular file Entry IDs are resolved
through AFP metadata only. Resource forks remain unsupported and continue to
return completion 0x9c.