Bug 493454 - Missing FUSE_COMPATIBLE_MAY_BLOCK markers
Summary: Missing FUSE_COMPATIBLE_MAY_BLOCK markers
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: 3.24 GIT
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Mark Wielaard
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-21 20:46 UTC by Mark Wielaard
Modified: 2024-10-05 12:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add missing FUSE_COMPATIBLE_MAY_BLOCKs (4.90 KB, text/plain)
2024-09-21 20:46 UTC, Mark Wielaard 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Wielaard 2024-09-21 20:46:18 UTC 
Created attachment 173943 [details]
Add missing FUSE_COMPATIBLE_MAY_BLOCKs

Various syscalls (in particular "at" variants) PRE handlers seem to be missing a FUSE_COMPATIBLE_MAY_BLOCK marker. This would block a fuss implementation when running under valgrind even with --sim-hints=fuse-compatible
Comment 1 Mark Wielaard 2024-10-05 12:50:24 UTC 
commit ddf397c024c80382f7a2f3a0d46d58fb839eef96
Author: Mark Wielaard <mark@klomp.org>
Date:   Sat Sep 21 22:27:24 2024 +0200

    Add missing FUSE_COMPATIBLE_MAY_BLOCKs
    
    Various syscalls (in particular "at" variants) PRE handlers were
    missing a FUSE_COMPATIBLE_MAY_BLOCK statement.
    
    Add it to the generic PRE handlers of access and statfs64. And the
    linux PRE handlers of mknodat, fchownat, futimesat, utimensat,
    utimensat_time64, renameat, renameat2, readlinkat, fchmodat,
    fchmodat2, faccessat and faccessat2.
    
    https://bugs.kde.org/show_bug.cgi?id=493454