diff options
| author | Paul Buetow <paul@buetow.org> | 2026-05-29 11:03:42 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-05-29 11:03:42 +0300 |
| commit | 9931b07600e504d99e45ee625a1cdadb2ba99840 (patch) | |
| tree | 1767f6a68e9127d5ad7acaad47b010b1421e644b /integrationtests/readwrite_test.go | |
| parent | 49662fd127b9d9db062a052a5249750a1fc1b8a3 (diff) | |
test(generate): lock in mincore BPF handler wiring (zv)
Audit of mincore(2) confirmed the existing tracing is correct: KindMem +
FamilyMemory, with addr=args[0], length=args[1], and both flags and length2
held at zero. args[2] is the userspace 'vec' output pointer, not a flags
value, so it is correctly NOT wired into ev->flags.
Add TestGenerateMemHandlerMincore to lock in this wiring and explicitly guard
against the historical mistake of mapping args[2] onto ev->flags the way
flags-bearing siblings (madvise/mlock2/mseal) do.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Diffstat (limited to 'integrationtests/readwrite_test.go')
0 files changed, 0 insertions, 0 deletions