diff options
| author | Paul Buetow <paul@buetow.org> | 2026-06-01 10:31:53 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-06-01 10:31:53 +0300 |
| commit | 8549884d1d957821b75dfbd5a4ff746667095f17 (patch) | |
| tree | c486c6643a86beceafd428a7e8b2d312162426f1 /internal | |
| parent | 1b59bbe42c13a2a60667dff51dc02e0c350434d7 (diff) | |
test(integration): add pwritev/pwritev2 retbytes coverage
Add write-side positional vectored coverage to close the remaining gap
in the pwrite64-family byte-accounting validation. The retbytes/readwrite
integration suite already exercised pwrite64 (scalar) and the read-side
preadv/preadv2, but the WRITE_CLASSIFIED byte attribution for the
vectored positional writes pwritev/pwritev2 was only covered by unit
tests, not end-to-end.
New ioworkload scenarios:
- readwrite-pwritev: issues pwritev (syscall.SYS_PWRITEV) writing a known
two-iovec payload at offset 0 to a temp file.
- readwrite-pwritev2: issues pwritev2 via the explicit syscall number
(328 amd64 / 287 arm64, mirroring preadv2SyscallNr) with offset 0 and
no flags.
New integration tests assert enter_pwritev/enter_pwritev2 fired and that
the attributed retbytes equal the exact iovec total, validating
WRITE_CLASSIFIED end-to-end. Both pass as root.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Diffstat (limited to 'internal')
0 files changed, 0 insertions, 0 deletions
