Debian Patches
Status for fuse3/3.17.2-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Fix_meson_function_tests.patch | [PATCH] Fix meson function tests Several meson tests were incorrectly failing Checking for function "static_assert" : NO (cached) Checking for function "pthread_setname_np" : NO (cached) Check usable header "#include <linux/close_range.h>" : NO (cached) These functions get now tested with compilation tests and get found on my system. Checking if "static_assert check" compiles: YES Checking if "pthread_setname_np check" compiles: YES Checking if "close_range check" compiles: YES |
Bernd Schubert <bschubert@ddn.com> | no | 2025-04-24 | ||
| meson.build-make-special_funcs-check-more-reliable.patch | [PATCH] meson.build: make special_funcs check more reliable Unfortunately while cross-compiling with build tools like Buildroot it happens to have repeated flags or anything that could lead to a warning. This way the check fails because of a warning not related to the special function. So let's use cc.links() and increase minimum meson_version to 0.60 since cc.links() has been added during that version. |
Giulio Benetti <giulio.benetti@benettiengineering.com> | no | 2025-04-25 | ||
| Make_conn-want-want_ext_conversion_non_fatal.patch | [PATCH] Make conn->want/want_ext conversion non fatal there are too many issues with conn->want and conn->want_ext conversion, for now just log a warning, but setting both flags is now not fatal anymore. |
Bernd Schubert <bschubert@ddn.com> | no | 2025-05-17 | ||
| Add-container_of-and-ROUND_UP-macros.patch | [PATCH] Add container_of and ROUND_UP macros Needed by follow up commits. container_of is actually just moved/consolidated to util.h. (cherry picked from commit c5a032b3410d7225ac0355355faa63565a209943) |
Bernd Schubert <bschubert@ddn.com> | no | 2025-04-15 | ||
| Fix-fuse_apply_conn_info_opts.patch | [PATCH] conn->want conversion: Fix fuse_apply_conn_info_opts() fuse_apply_conn_info_opts() was applying to 'want_ext', which would cause conflicts with 'want' if the application applied its own flags to 'conn->want'. Solution is: - to move fuse_{set,unset,get}_feature_flag and convert_to_conn_want_ext() to fuse_lowlevel.c and to define them as part of the public API, although convert_to_conn_want_ext() should not be used - it is currently needed to be a public function due as it needs to be defined for the tests. Related to https://github.com/libfuse/libfuse/issues/1171 and https://github.com/libfuse/libfuse/pull/1172. |
Bernd Schubert <bschubert@ddn.com> | no | 2025-05-18 | ||
| Fix-the-close_range-ifdef.patch | [PATCH] fusermount: Fix the close_range ifdef This fixes commit 82bcd818 That commit had removed HAVE_LINUX_CLOSE_RANGE in meson generation, but didn't remove the usage in fusermount.c - fusermount was then not using the close_range syscall. |
Bernd Schubert <bernd@bsbernd.com> | no | 2025-07-15 | ||
| memfs_ll-fix-deadlock.patch | [PATCH] memfs_ll: fix deadlock in truncate operation Remove redundant mutex lock acquisition in the truncate() method to prevent deadlock. The issue occurs when memfs_setattr() already holds the mutex lock and then calls truncate(), which attempts to acquire the same lock again. |
Long Li <leo.lilong@huawei.com> | no | 2025-07-16 |