fanotify_mark
Implemented in Antinomie 0.7.0 · Syscall list
Synopsis
Section titled “Synopsis”long fanotify_mark(int fanotify_fd, unsigned int flags, u64 mask, int fd, const char *pathname);| Number (x86-64) | 301 |
| ABI | common |
| Kernel entry point | sys_fanotify_mark |
This is the raw kernel prototype from the pinned Linux 6.12.94 schema, not the libc wrapper.
Description
Section titled “Description”Adds, removes or changes the filesystem objects a fanotify group watches.
Arguments
Section titled “Arguments”| Name | Type | Meaning |
|---|---|---|
fanotify_fd (arg0) |
int |
File descriptor of a fanotify group. |
flags (arg1) |
unsigned int |
Option flags that change the behavior of the call. |
mask (arg2) |
u64 |
Bit mask. |
fd (arg3) |
int |
File descriptor to operate on. |
pathname (arg4) |
const char * |
Path, as a NUL-terminated string in user memory. |
Return value
Section titled “Return value”On success: 0.
In an Antinomie trace the Return column and the ret filter field show the raw kernel return value. On failure that is the negative errno, for example -2 for ENOENT, not the -1 plus errno that the libc wrapper gives. syscall.errno holds the positive errno and syscall.success is false.
Common errors
Section titled “Common errors”| Raw return | Name | Meaning |
|---|---|---|
-9 |
EBADF |
A file descriptor is not valid for this operation. |
-22 |
EINVAL |
An argument is invalid. |
-2 |
ENOENT |
A path component or the named object does not exist. |
Man page
Section titled “Man page”Captured by Antinomie
Section titled “Captured by Antinomie”Coverage mark: Implemented. Every pointer argument has a capture rule in the pinned kernel patch and none of them records a “no decoder”, “address only” or “not observed” gap on any code path. Individual values can still be incomplete on a particular call; see the capture statuses.
Every call is recorded as an Entry record (the six argument words and the pointees copied at entry) and an Exit record (the return value and the pointees copied at exit).
Arguments
Section titled “Arguments”| Argument | When | How | Recorded field key | Condition |
|---|---|---|---|---|
fanotify_fd (arg0) |
Entry | raw scalar word | args.0, args.fanotify_fd |
|
flags (arg1) |
Entry | raw scalar word; Syscall Trace also decodes it into flag names (fanotify_mark group), listing unknown bits separately |
args.1, args.flags |
|
mask (arg2) |
Entry | raw scalar word | args.2, args.mask |
|
fd (arg3) |
Entry | raw scalar word | args.3, args.fd |
|
pathname (arg4) |
Entry | the pointer itself, as a raw word | args.4, args.raw[4] |
|
| ↳ pointee | Entry | NUL-terminated string, up to 4,096 bytes (PATH_MAX) | arg4.path |
always |
Filter fields
Section titled “Filter fields”- Result:
ret,syscall.errno,syscall.success,syscall.duration_ns. - Argument words:
args.fanotify_fd(arg0),args.flags(arg1),args.mask(arg2),args.fd(arg3),args.pathname(arg4);args.0toargs.5by position. - Captured strings: the
args.<name>field of a path argument, andargs.path, give the captured text instead of the pointer.
See Syscall Trace filter for the full syntax.
For what the capture statuses mean, see Capture statuses. For what is never recorded, see Known gaps.