diff options
| author | Paul Buetow <paul@buetow.org> | 2026-05-30 22:30:26 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-05-30 22:30:26 +0300 |
| commit | 75d00f479d333476990ff18f7427905bb09d49f0 (patch) | |
| tree | a1aea501073236677a002685b921d7d6c7a42352 /internal/eventloop_security_test.go | |
| parent | 136c4dfb6846595b98cf2b04a93525ce91d86d5e (diff) | |
test(generate): lock in semctl handler as KindSysVOp/FamilyIPC
Audit of semctl(2) confirmed the implementation is correct: it is
classified KindSysVOp in FamilyIPC, consistent with its SysV
control-syscall siblings msgctl/shmctl (and semget/semop/semtimedop).
The enter handler emits a null_event and captures no argument, so the
semid at args[0] -- a System V IPC identifier, NOT a file descriptor --
is correctly not recorded as an fd. The exit handler reports the raw
op-dependent int status (value or -1) as UNCLASSIFIED, never a byte
count.
The classification table already covered semctl, but only msgctl's
generated handler body was directly asserted. Add dedicated lock-in
tests mirroring TestGenerateMsgctlHandler:
- TestGenerateSemctlHandler: enter emits null_event, no ctx->args[]
capture, no ev->fd; exit ret_type UNCLASSIFIED.
- TestClassifyRetSemctlUnclassified: ret is UNCLASSIFIED.
No classification, generated C, docs, or runtime behavior changed
(mage generate produces no diff), so this is a test-only addition.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Diffstat (limited to 'internal/eventloop_security_test.go')
0 files changed, 0 insertions, 0 deletions
