update ZFS to get better work-around for UBSAN bounds-checking
We have a slightly better fix where only a few targeted ZFS module parts are added to the UBSAN ignore-list, so the rest of the kernel still gets exposure. Link: https://github.com/openzfs/zfs/pull/15510 Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
parent
b0ac1e9734
commit
c0a8921e19
1
debian/rules
vendored
1
debian/rules
vendored
@ -99,7 +99,6 @@ PMX_CONFIG_OPTS= \
|
|||||||
-e CONFIG_PAGE_TABLE_ISOLATION \
|
-e CONFIG_PAGE_TABLE_ISOLATION \
|
||||||
-e CONFIG_ARCH_HAS_CPU_FINALIZE_INIT \
|
-e CONFIG_ARCH_HAS_CPU_FINALIZE_INIT \
|
||||||
-d CONFIG_GDS_FORCE_MITIGATION \
|
-d CONFIG_GDS_FORCE_MITIGATION \
|
||||||
-d UBSAN_BOUNDS \
|
|
||||||
|
|
||||||
debian/control: $(wildcard debian/*.in)
|
debian/control: $(wildcard debian/*.in)
|
||||||
sed -e 's/@@KVNAME@@/$(KVNAME)/g' < debian/proxmox-kernel.prerm.in > debian/$(PMX_KERNEL_PKG).prerm
|
sed -e 's/@@KVNAME@@/$(KVNAME)/g' < debian/proxmox-kernel.prerm.in > debian/$(PMX_KERNEL_PKG).prerm
|
||||||
|
@ -1 +1 @@
|
|||||||
Subproject commit aa99285dda7f91add062b177fe1a811334fdd4fb
|
Subproject commit 88fd6e053b4cbfa197d04d4263eb176795b70977
|
Loading…
Reference in New Issue
Block a user