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

tests: record standalone AFP xattr backend smoke success

Browse Source
This commit is contained in:
Mario Fetka
2026-05-31 04:35:31 +00:00
parent aa041a405b
commit 711dceb42a
2 changed files with 45 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
tests/linux/README.md
View File

@@ -1137,3 +1137,40 @@ 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.
## Standalone AFP xattr backend smoke success
The AFP metadata backend no longer depends on Netatalk/libatalk for the
currently implemented metadata. After the standalone mars_nwe xattr backend
change, the full AFP smoke suite was rerun against `SYS:PUBLIC/pmdflts.ini`
and completed successfully.
Verified smoke run:
```text
AFP Entry ID From Path Name
AFP Entry ID path=SYS:PUBLIC/pmdflts.ini request_path=SYS:PUBLIC/pmdflts.ini dir_handle=0 entry_id=0x05811b2a (92347178)
AFP Open File Fork by Entry ID
AFP Open File Fork path=SYS:PUBLIC/pmdflts.ini entry_id=0x05811b2a 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=0x145f0c8a handle=1 fork=0 access=0x02 fork_len=0 entry-id-only
Linux xattr: AFP FinderInfo
user.org.mars-nwe.afp.finder-info=0x544558544d415253000000000000000000000000000000000000000000000000
Linux xattr: AFP Entry ID
user.org.mars-nwe.afp.entry-id=0x0100000005811b2a
AFP-only attributes xattr is absent; this is expected when the tested Hidden/System/Archive bits are stored through the NetWare attribute path.
Summary: failures=0
```
This confirms that Entry ID and FinderInfo metadata are served from the
mars_nwe-owned AFP xattrs, while Hidden/System/Archive attributes and the
timestamp fields continue to use the existing NetWare metadata paths. AFP
remains behind the existing build configuration; this smoke only records that
the implemented AFP endpoints no longer need a Netatalk/libatalk metadata
backend when xattr support is enabled.