| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 01-sm-notify-in-sbin.patch | =================================================================== | no | ||||
| 25-systemd-daemon-paths.patch | Adjust program paths in systemd units | Martin Pitt <martin.pitt@ubuntu.com> | no | |||
| multiarch-kerberos-paths.patch | Support multiarch kerberos paths (Closes: #642797). diff -Naurp nfs-utils.orig/aclocal/kerberos5.m4 nfs-utils/aclocal/kerberos5.m4 |
Luk Claes <luk@debian.org> | no | |||
| blkmapd-fix-coredump-in-bl_add_disk.patch | blkmapd: fix coredump in bl_add_disk The serial->data is not malloced separately (just part of the serial), so it can't be freed. The bl_serial has its own free function. Use it. |
Lixiaokeng <lixiaokeng@huawei.com> | no | debian | https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=c1c35487aba2cec828d9b8a1be9043000beadea5 | 2022-10-24 |
| Revert-configure-make-modprobe.d-directory-configura.patch | [PATCH 1/4] Revert "configure: make modprobe.d directory configurable" This reverts commit 7d76dd2e6f09a141eb6303b7343baa5c4f9c85ad. This is part of the full revert of adding support via modprobe.d configuration to set sysctl settings of NFS-related modules when loading the modules. The approach caused problems with sysctl from busybox and with kmod as reported in Debian (https://bugs.debian.org/1024082). |
Salvatore Bonaccorso <carnil@debian.org> | no | 2022-12-05 | ||
| Revert-modprobe-protect-against-sysctl-errors.patch | [PATCH 2/4] Revert "modprobe: protect against sysctl errors" This reverts commit 5e60e38aa4ba251ef66610514be5f45c41519e0f. This is part of the full revert of adding support via modprobe.d configuration to set sysctl settings of NFS-related modules when loading the modules. The approach caused problems with sysctl from busybox and with kmod as reported in Debian (https://bugs.debian.org/1024082). |
Salvatore Bonaccorso <carnil@debian.org> | no | 2022-12-05 | ||
| Revert-systemd-Apply-all-sysctl-settings-when-NFS-re.patch | [PATCH 3/4] Revert "systemd: Apply all sysctl settings when NFS-related modules are loaded" This reverts commit afc7132dfb212ac1f676a5ac36d29a9e06325645. The approach caused problems with sysctl from busybox and with kmod as reported in Debian (https://bugs.debian.org/1024082). |
Salvatore Bonaccorso <carnil@debian.org> | no | 2022-12-05 | ||
| systemd-Apply-all-sysctl-settings-through-udev-rule-.patch | [PATCH 4/4] systemd: Apply all sysctl settings through udev rule when NFS-related modules are loaded sysctl settings (e.g. /etc/sysctl.conf and others) are normally loaded once at boot. If the module that implements some settings is no yet loaded, those settings don't get applied. Various NFS modules support various sysctl settings. If they are loaded after boot, they miss out. Add a new udev rule configuration to udev/rules.d/60-nfs.rules to apply the relevant settings when the modules are loaded. Placing it in the systemd directory similarly as the choice for the original commit afc7132dfb21 ("systemd: Apply all sysctl settings when NFS-related modules are loaded"). |
Salvatore Bonaccorso <carnil@debian.org> | no | 2022-12-05 | ||
| auth-rpcgss-module.service-Don-t-fail-inside-linux-c.patch | [PATCH] auth-rpcgss-module.service: Don't fail inside linux container. Only try to load the auth_rpcgss kernel module if we are not executing inside a Linux container. Otherwise, the auth-rpcgss-module service will fail inside a Linux container as the loading of kernel modules is forbidden for the container. Thus, the "/sbin/modprobe -q auth_rpcgss" call will fail even if the auth_rpcgss kernel module is already loaded. This situation occurs when the container host has already loaded the auth_rpcgss kernel module to enable kerberized NFS service for its containers. This behavior has been tested with kmod up to version 30+20220630-3 (current in bookworm as of 2022-09-20). |
Joachim Falk <joachim.falk@gmx.de> | no | debian | 2022-12-05 | |
| systemd-Don-t-degrade-system-state-for-nfs-clients-w.patch | systemd: Don't degrade system state for nfs-clients when krb5 keytab present but not containing the nfs/<FQDN> principal The nfs-client.target requires the auth-rpcgss-module.service, which in turn requires the rpc-svcgssd.service. However, the rpc.svcgssd daemon is unnecessary for an NFS client, even when using Kerberos security. Moreover, starting this daemon with its default configuration will fail when no nfs/<host>@REALM principal is in the Kerberos keytab. Thus, resulting in a degraded system state for NFS client configurations without nfs/<host>@REALM principal in the Kerberos keytab. However, this is a perfectly valid NFS client configuration as the nfs/<host>@REALM principal is not required for mounting NFS file systems. This is even the case when Kerberos security is enabled for the mount! Installing the gssproxy package hides this problem as this disables the rpc-svcgssd.service. |
Joachim Falk <joachim.falk@gmx.de> | no | debian | https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=5faf98a62843d1cda2a0fe15e0878fa1281e42b8 | 2023-01-10 |