Tip XFAIL residuals: t0011 allsquash and t0013 ACL

[ericvh]

After #26, harness eval is clean (unexpected: 0). Remaining FAILs look like real diod/v9fs tip behavior, not mount/harness plumbing (t0010 and t0020/t0021 mounts already green).

Residuals

• t0011-v9fs-allsquash.t — several FAIL (root/nobody create/chmod expectations under allsquash) + automake ERROR: exited with status 1
• t0013-v9fs-acl.t — setfacl/getfacl round-trips FAIL on client and server + same ERROR wrapper

Evidence

• https://github.com/v9fs/test/actions/runs/32929975795

Intent

Keep these as intentional XFAILs in diod/xfail.txt. Do not treat them as harness regressions until tip allsquash and ACL are diagnosed.

[ericvh]

Diagnosed from 32929975795 (diod-regression-logs: diod-test-suite.log + the two .diod.log files). These stay intentional XFAILs. Automake ERROR: exited with status 1 is just test_diodrun wrapping FAIL (client rc=1). ulimit in the chroot is noise.

t0011 allsquash — squash is working; the owner assertion is not

diod says:

Dropped root, running as nobody
Anyone can attach and access files as nobody

Rmkdir/Rgetattr for userdir, rootdir, and nobodydir are all uid 65534 gid 65534. Attaches are n_uname 1001 (runner), 0 (root), 65534 (nobody).

The FAIL is the server-side check:

test "$($PATH_STAT -c "%u:%g" exp/rootdir)" = "$(id -u):$(id -g)"

That expects squashuser == test uid (1001). Default squashuser is nobody. Cascade: steps 5–6 fail the owner check (mkdir itself succeeded); 7–8 runner cannot write 0755 nobody-owned dirs; 11 test_must_fail nobody-create succeeds; 12 runner chmod 777 is not the owner.

t0002-basic-allsquash.t never asserts exp/ ownership equals id -u. t0012 (access=client) is green aside from XATTR skips — not an access=user mount regression.

Next: --squashuser=$(id -un) vs changing the assertion to 65534. Decide whether the test or the default squashuser is wrong.

t0013 ACL — posixacl mount works; ACL xattrs are EOPNOTSUPP

Mount -o posixacl PASSes. Every Txattrwalk of system.posix_acl_access / _default on /tmp/sharness-trash/t0013-v9fs-acl/exp/... returns ecode 95 (EOPNOTSUPP). There is no Txattrcreate. setfacl -m / default-ACL steps FAIL; setfacl -x PASSes (nothing to remove).

Same guest skipped t0012 user/trusted/security xattr cases (missing XATTR): local getfattr on a trash file already reports Operation not supported. Kernel publish enables 9P_FS_POSIX_ACL, 9P_FS_XATTR, FS_POSIX_ACL, TMPFS_POSIX_ACL, but not TMPFS_XATTR explicitly. t0013 has no XATTR prereq, so it FAILs instead of SKIP.

Next: in-guest setfacl on a /tmp file. If that is EOPNOTSUPP, enable TMPFS_XATTR (and confirm TMPFS_POSIX_ACL actually landed) or put sharness trash on ext4.

Keep diod/xfail.txt as-is until those two experiments.

[ericvh]

Mapped as two independent residuals on the private a-team forge (not a product-code change):

• Work slice: Formulate first slice: map t0011/t0013 tip residuals (v9fs/test#28) agent-team#1
• Mapping PR (draft): Map t0011/t0013 tip residuals (M0 evidence) agent-team#2

Pins: linux v7.2 (8d3ae59288f1e7d58d76558a6ee96d533bc5019f), harness 94b2182f54b30a073d893990db8f64e69f0d911a, diod de51d1ee1bd5ccf1d8c16b96227c8bb03ec50106, run 32929975795.

Keep the XFAIL list until separate t0011 and t0013 implementation slices PASS.