diff options
| author | João Paredes <joaommp@yahoo.com> | 2026-03-02 02:55:39 +0000 |
|---|---|---|
| committer | Dave Kleikamp <dave.kleikamp@oracle.com> | 2026-03-11 10:57:52 -0500 |
| commit | 679330e4a7af1d102d035b13b2b9d41bc1dfbbf7 (patch) | |
| tree | 482a9255ecc70d091bd9fef7c63b4c43452d3024 /tools/perf/scripts/python/bin/netdev-times-report | |
| parent | ca5848ae87d24886a7886f5a22278bd4045c15f8 (diff) | |
JFS: always load filesystem UUID during mount
The filesystem UUID was only being loaded into super_block sb when an
external journal device was in use. When mounting without an external
journal, the UUID remained unset, which prevented the computation of
a filesystem ID (fsid), which could be confirmed via `stat -f -c "%i"`
and thus user space could not use fanotify correctly.
A missing filesystem ID causes fanotify to return ENODEV when marking
the filesystem for events like FAN_CREATE, FAN_DELETE, FAN_MOVED_TO,
and FAN_MOVED_FROM. As a result, applications relying on fanotify
could not monitor these events on JFS filesystems without an external
journal.
Moved the UUID initialization so it is always performed during mount,
ensuring the superblock UUID is consistently available.
Signed-off-by: João Paredes <joaommp@yahoo.com>
Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/netdev-times-report')
0 files changed, 0 insertions, 0 deletions