| Summary: | Missing FUSE_COMPATIBLE_MAY_BLOCK markers | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Mark Wielaard <mark> |
| Component: | general | Assignee: | Mark Wielaard <mark> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | fweimer, sam |
| Priority: | NOR | ||
| Version First Reported In: | 3.24 GIT | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=493507 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Add missing FUSE_COMPATIBLE_MAY_BLOCKs | ||
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 |
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