| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 01-remove-use-systemd-guards-around-several.diff | Remove USE_SYSTEMD guards around several scripts that should always get installed. The build-time detection of systemd support only appears to work when usrmerge is enabled, resulting in different packages on usrmerge vs. non-usrmerge systems, breaking reproducible builds. |
Vagrant Cascadian <vagrant@reproducible-builds.org> | no | 2020-08-19 | ||
| 02-systemd-service.diff | # Fix PID file location and add a generic hardening feature. # Use another KillMode to fix #995303 diff -Naur glusterfs-9.4.orig/extras/systemd/glusterd.service.in glusterfs-9.4/extras/systemd/glusterd.service.in |
no | ||||
| 03-systemd-environment-file.diff | # Use environment configuration file for glusterd. # Closes: #1002799 diff -Naur glusterfs-10.0.orig/extras/systemd/glusterd.service.in glusterfs-10.0/extras/systemd/glusterd.service.in |
no | ||||
| 06-spelling-error.diff | # Fix another spelling error. diff -Naur glusterfs-7.5.orig/xlators/mount/fuse/src/fuse-bridge.c glusterfs-7.5/xlators/mount/fuse/src/fuse-bridge.c |
no | ||||
| 07-spelling-error.diff | # Fix one spelling error. diff -Naur glusterfs-8.0.orig/glusterfsd/src/glusterfsd-messages.h glusterfs-8.0/glusterfsd/src/glusterfsd-messages.h |
no | ||||
| 08-bash-term-in-posix-shell.diff | # Workaround these warnings: # glusterfs-common: bash-term-in-posix-shell '${gfid:0:2}' [usr/lib/x86_64-linux-gnu/glusterfs/gfind_missing_files/gfid_to_path.sh:24] # glusterfs-common: bash-term-in-posix-shell '/dev/tcp' [usr/lib/x86_64-linux-gnu/glusterfs/gfind_missing_files/gfind_missing_files.sh:32] diff -Naur glusterfs-10.2.orig/tools/gfind_missing_files/gfid_to_path.sh glusterfs-10.2/tools/gfind_missing_files/gfid_to_path.sh |
no | ||||
| 09-CVE-2023-26253.diff | [PATCH] fuse: Resolve asan bug in during receive event notification (#4024) The fuse xlator notify function tries to assign data object to graph object without checking an event. In case of upcall event data object represents upcall object so during access of graph object the process crashed for asan build. specifically to fuse xlator > Fixes: #3954 > Change-Id: I6b2869256b26d22163879737dcf163510d1cd8bf > Signed-off-by: Mohit Agrawal moagrawa@redhat.com > (Reviewed on upstream link #4019) |
mohit84 <moagrawa@redhat.com> | no | 2023-03-30 |