diff options
| author | Brahmajit Das <[email protected]> | 2025-06-30 11:02:41 +0000 |
|---|---|---|
| committer | Jan Kara <[email protected]> | 2025-07-28 16:14:15 +0000 |
| commit | 3193e8942fc7f70ba3c872a988a0c15f98818bd2 (patch) | |
| tree | 494bd13c15f14029b732266db71a34ff81467986 /fs/file_table.c | |
| parent | fanotify: sanitize handle_type values when reporting fid (diff) | |
| download | kernel-3193e8942fc7f70ba3c872a988a0c15f98818bd2.tar.gz kernel-3193e8942fc7f70ba3c872a988a0c15f98818bd2.zip | |
samples: fix building fs-monitor on musl systems
samples/fanotify/fs-monitor.c:22:9: error: unknown type name '__s32'
22 | __s32 error;
| ^~~~~
samples/fanotify/fs-monitor.c:23:9: error: unknown type name '__u32'
23 | __u32 error_count;
| ^~~~~
samples/fanotify/fs-monitor.c: In function 'handle_notifications':
samples/fanotify/fs-monitor.c:98:50: error: 'fsid_t' has no member named 'val';
did you mean '__val'?
98 | fid->fsid.val[0],
fid->fsid.val[1]);
| ^~~
| __val
samples/fanotify/fs-monitor.c:98:68: error: 'fsid_t' has no member named 'val';
did you mean '__val'?
98 | fid->fsid.val[0],
fid->fsid.val[1]);
| ^~~
| __val
This is due to sys/fanotify.h on musl does not include
linux/fanotify.h[0] unlike glibc which includes it. This also results in
fsid not being of type __kernel_fsid_t, rather the libc's definition of
it which does not have val, but instead __val.
[0]: https://git.musl-libc.org/cgit/musl/tree/include/sys/fanotify.h
Signed-off-by: Brahmajit Das <[email protected]>
Signed-off-by: Jan Kara <[email protected]>
Link: https://patch.msgid.link/[email protected]
Diffstat (limited to 'fs/file_table.c')
0 files changed, 0 insertions, 0 deletions