diff options
| author | Paul Buetow <paul@buetow.org> | 2026-06-02 09:51:14 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-06-02 09:51:14 +0300 |
| commit | 88769d471981911242dda27ed75d92866b2acf05 (patch) | |
| tree | 6acb367c7c8a41d6a000172d29485361bc9d1ebe /internal/tracepoints | |
| parent | 3af826ec72c7a520f0993c0fa8842d347eba7fed (diff) | |
fix(classify): assign fanotify_init to FamilyIPC, not Misc
fanotify_init(2) creates and initializes an fanotify notification group
and returns an event-queue file descriptor. It is the direct analog of
inotify_init1 (both are filesystem-event notification facilities whose
group-creating syscall is a flags-taking fd-creator). inotify_init/
inotify_init1 are FamilyIPC alongside the other fd-based event-notification
primitives (eventfd, signalfd, timerfd, userfaultfd), yet fanotify_init
fell through to FamilyMisc by omission from the explicit family table -- an
alarm/adjtimex-style misclassification inconsistent with its siblings.
Add fanotify_init to the IPC family map and regenerate. Kind
(KindEventfd, flags at args[0]) and ret (UNCLASSIFIED, returned fd captured
via the fd mechanism) were already correct and are unchanged. fanotify_mark
stays in Misc (path-marking, not fd creation). Docs plan updated to keep
the docs-drift test in sync.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Diffstat (limited to 'internal/tracepoints')
| -rw-r--r-- | internal/tracepoints/generated_tracepoints.go | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/internal/tracepoints/generated_tracepoints.go b/internal/tracepoints/generated_tracepoints.go index 1fa2a27..1ca5f85 100644 --- a/internal/tracepoints/generated_tracepoints.go +++ b/internal/tracepoints/generated_tracepoints.go @@ -786,7 +786,7 @@ var syscallFamilies = map[string]string{ "faccessat2": "FS", "fadvise64": "FS", "fallocate": "FS", - "fanotify_init": "Misc", + "fanotify_init": "IPC", "fanotify_mark": "Misc", "fchdir": "FS", "fchmod": "FS", |