Debian Patches

Status for zfs-linux/2.3.2-2~bpo12+2

Patch Description Author Forwarded Bugs Origin Last update
1000-dont-symlink-zed-scripts.patch track default symlinks, instead of symlinking not-needed
1001-Prevent-manual-builds-in-the-DKMS-source.patch Block manual building in the DKMS source tree. To avoid messing up future DKMS builds and the zfs installation,
block manual building of the DKMS source tree.
unknown not-needed ubuntu 2017-10-06
1002-Check-for-META-and-DCH-consistency-in-autoconf.patch check for META and dch consistency in autoconf not-needed
1003-relocate-zvol_wait.patch relocate the executable path=================================================================== not-needed
1005-enable-zed.patch Enable zed emails The OpenZFS event daemon monitors pools. This patch enables the email
sending function by default (if zed is installed). This is consistent with
the default behavior of mdadm.
Richard Laager <rlaager@wiktel.com> not-needed
1006-zed-service-bindir.patch Fix the path to the zed binary on the systemd unit. We install zed into /usr/sbin manually meanwhile the upstream default
is installing it into /sbin.
Ubuntu packages also install zed to /usr/sbin, but they ship their own
zfs-zed unit.
Chris Dos <chris@chrisdos.com> not-needed debian
1007-dkms-pkgcfg.patch not-needed
2100-zfs-load-module.patch explicitly load the ZFS module via systemd service Ubuntu developers not-needed
3100-remove-libzfs-module-timeout.patch Reduce the timeout to zero seconds when running in a container (LP: #1760173) When inside a lxd container with zfs storage, zfs list or zpool status
appears to hang, no output for 10 seconds. Check if we are inside a
container and set the timeout to zero in this specific case.
not-needed upstream ubuntu
force-verbose-rules.patch force libtool to produce verbose output Mo Zhou not-needed
move-arcstat-1-to-8.patch commit c999ab77f8dad6c6655007baebe9c7992d6fe206

Move arcstat(1) to arcstat(8) to avoid conflict with binary package nordugrid-arc-client.
We regenerate Makefile.in, so we don't have to modify them explicitly here.
Mo Zhou <cdluminate@gmail.com> not-needed 2021-01-15
skip-on-PREEMPT_RT.patch do not attempt to build the modules on PREEMPT_RT kernels Andreas Beckmann <anbe@debian.org> yes debian upstream 2024-08-08
cross-compile.patch Fix cross-compile of the dkms module. Dimitri John Ledkov <dimitri.ledkov@canonical.com> no ubuntu
ubuntu/zfs-mount-container-start.patch Start zfs-mount.service after zfs-load-module.service, and if zfs module was actually loaded. This should allow installation of probert in
containers, which pulls in zfs-linux utilities.
Dimitri John Ledkov <xnox@ubuntu.com> no
fix-pyzfs-version.patch Fix pyzfs version Python does not think x.y.z~rcN is a valid version. Make it happy. Shengqi Chen <harry-chen@outlook.com> not-needed 2024-10-11
BUILD_EXCLUSIVE_KERNEL_MIN.patch set BUILD_EXCLUSIVE_KERNEL_MIN in dkms.conf Andreas Beckmann <anbe@debian.org> no
upstream/0001-Fix-2-bugs-in-non-raw-send-with-encryption.patch [PATCH] Fix 2 bugs in non-raw send with encryption
Bisecting identified the redacted send/receive as the source of the bug
for issue #12014. Specifically the call to
dsl_dataset_hold_obj(&fromds) has been replaced by
dsl_dataset_hold_obj_flags() which passes a DECRYPT flag and creates
a key mapping. A subsequent dsl_dataset_rele_flag(&fromds) is missing
and the key mapping is not cleared. This may be inadvertedly used, which
results in arc_untransform failing with ECKSUM in:
arc_untransform+0x96/0xb0 [zfs]
dbuf_read_verify_dnode_crypt+0x196/0x350 [zfs]
dbuf_read+0x56/0x770 [zfs]
dmu_buf_hold_by_dnode+0x4a/0x80 [zfs]
zap_lockdir+0x87/0xf0 [zfs]
zap_lookup_norm+0x5c/0xd0 [zfs]
zap_lookup+0x16/0x20 [zfs]
zfs_get_zplprop+0x8d/0x1d0 [zfs]
setup_featureflags+0x267/0x2e0 [zfs]
dmu_send_impl+0xe7/0xcb0 [zfs]
dmu_send_obj+0x265/0x360 [zfs]
zfs_ioc_send+0x10c/0x280 [zfs]

Fix this by restoring the call to dsl_dataset_hold_obj().

The same applies for to_ds: here replace dsl_dataset_rele(&to_ds) with
dsl_dataset_rele_flags().

Both leaked key mappings will cause a panic when exporting the
sending pool or unloading the zfs module after a non-raw send from
an encrypted filesystem.

Closes #12014
Closes #17340
(cherry picked from commit ea74cdedda8b9575d7e94198d38f12943ac41343)
George Amanakis <gamanakis@gmail.com> no 2025-05-19
upstream/0002-ARC-Avoid-overflows-in-arc_evict_adj.patch [PATCH] ARC: Avoid overflows in arc_evict_adj() (#17255)
With certain combinations of target ARC states balance and ghost
hit rates it was possible to get the fractions outside of allowed
range. This patch limits maximum balance adjustment speed, which
should make it impossible, and also asserts it.

Fixes #17210
Signed-off-by: Alexander Motin <mav@FreeBSD.org>
Sponsored by: iXsystems, Inc.
(cherry picked from commit b1ccab17213b38aa269e85c6b371d69eb25b6ca9)
Alexander Motin <mav@FreeBSD.org> no 2025-05-06
upstream/0003-Sort-the-blocking-snapshots-list.patch [PATCH] Sort the blocking snapshots list #12751 (#17264)
When multiple snapshots prevent the destruction/rollback of the
respective dataset/snapshot/volume via zfs destroy or zfs rollback,
the error message does not list the blocking snapshots sorted
according to their order of creation. This causes inconvenience and can
lead to confusion, and also creates a contrast with a returned message
from zfs list -t snap function.


(cherry picked from commit 27f3d94940490d891c70e0c148f80d0c0ce09ed4)
Artem <artem.vlasenko@ossrevival.org> no 2025-05-02
upstream/0004-Prefer-embedded-blocks-to-dedup.patch [PATCH] Prefer embedded blocks to dedup
Since embedded blocks introduction 11 years ago, their writing was
blocked if dedup is enabled. After searching through the modern
code I see no reason for this restriction to exist. Same time
embedded blocks are dramatically cheaper. Even regular write of
so small blocks would likely be cheaper than deduplication, even
if the last is successful, not mentioning otherwise.

Signed-off-by: Alexander Motin <mav@FreeBSD.org>
Sponsored by: iXsystems, Inc.
Closes #17113
(cherry picked from commit 09f4dd06c3e3275e1aa0b8d12a894cf140d19c3f)
Alexander Motin <mav@FreeBSD.org> no 2025-03-13
upstream/0005-Add-more-descriptive-destroy-error-message.patch [PATCH] Add more descriptive destroy error message
Reviewed by: Attila Fülöp <attila@fueloep.org>
(cherry picked from commit 37a3e26552158cb30a0bac0719c8dca40e22f245)
Artem-OSSRevival <artem.vlasenko@ossrevival.org> no 2025-04-24
upstream/0006-Export-correct-symbols-for-Lustre-Direct-IO.patch [PATCH] Export correct symbols for Lustre Direct I/O
Originally the Lustre ZFS OSD code was going to use zfs_uio_t structs
for supporting Direct I/O with ZFS. However, this has changed to using
abd_t structs instead. This exports the proper symbols that will be used
by the Lustre ZFS OSD code.

Closes #17256
(cherry picked from commit 7031a48c7077822bf6e3c53b3e753155ee7fbc1c)
Brian Atkinson <batkinson@lanl.gov> no 2025-04-24

All known versions for source package 'zfs-linux'

Links