From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] lz4: Update to version 1.11.1
Date: Thu, 12 Nov 2026 18:04:57 +0100 [thread overview]
Message-ID: <20261112170458.2062476-5-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20261112170458.2062476-1-adolf.belka@ipfire.org>
- Update from version 1.10.0 to 1.11.1
- Update of rootfile
- Although there are no CVE's some of the bug fixes look like security related issues.
- Changelog
1.11.1
fix : `LZ4_resetStreamHC()` could write out of bounds at levels >= 10, on a
state containing garbage (since v1.11.0)
perf : faster decompression on ppc64 (+12% to +24% on silesia),
`LZ4_FAST_DEC_LOOP` enabled, by @runlevel5
perf : `lz4 -l` compresses small files up to 10x faster : no more threads
than blocks
api : restored the unprefixed lz4frame enums and types
(`LZ4F_ENABLE_OBSOLETE_ENUMS`), employed by zstd, now deprecated (compilation
warning), reported by @diizzyy
cli : help (`-h`, `-H`, `--help`) outputs to stdout, requested by @tansy
cli : `--list` reads standard input again (since v1.10.0)
cli : various fixes (`--list`, `--stdout`, `--force`, multiple inputs,
Windows pipes, modification time, output creation), by @lee3Q, @immanuwell
and @rudycelekli
build: `lz4file.h` usable from cmake (since v1.10.0) and meson installations,
reported by @rudycelekli
build: MinGW builds with clang and lld (since v1.11.0), reported by @tansy
build: `make` with `BUILD_STATIC=no` or `BUILD_SHARED=no` (since v1.11.0),
by @xry111
1.11.0
fix : data corruption in valid usage : ring buffer decoding
(`LZ4_decoderRingBufferSize()`, since v1.9.0), rare cases of streaming or
`destSize` compression, one reported by @freedom-winds
fix : single-thread `lz4` could truncate the decoding of concatenated frames
with block checksums
fix : multithreaded decompression could write out of bounds after 2^31
frames (since v1.10.0), by @arshsmith1
fix : `LZ4F_compressBegin_usingDict()` ignored the dictionary with
independent blocks
fix : some periodic data compressed up to 30x worse at fast levels, and very
slowly at level 12, reported by @martinus
fix : invalid arguments (negative sizes, `NULL`, invalid `blockSizeID`,
extreme levels) no longer crash nor overflow, by @arthuz-th,
@jaypatrickhoward, @louislafosse, @akashdeshmukh-git, @rinsuki
fix : lz4file reports truncated files and write failures, and accepts
files < 19 bytes, by @axiqia
perf : faster decompression on aarch64 and x86-64 (up to +19%, +4% on
silesia.tar), `LZ4_FAST_DEC_LOOP` on aarch64 with clang and on riscv64, by
@Nicoshev and @arpadpanyik-arm
perf : faster compression of small blocks at fast levels, with reused states
(up to +80%) or dictionaries (up to +35%), partly proposed by @BiplabRaut
perf : faster levels 11 and 12 (+8% to +27%), level 2 compresses ~0.8% better
perf : x86 builds avoid the JCC erratum : up to +12% compression and +31%
decompression on Intel Skylake-family cpus
api : multithreaded lz4frame compression (experimental
`LZ4F_preferences_t.nbWorkers`) : output independent of the nb of workers
and of the context's history
api : random access within frames and lz4 files : `LZ4F_resumeFrame()`,
`LZ4F_seek()`, `LZ4F_tell()` (static)
api : `LZ4_decompress_safe()` returns distinct error codes : `-1` malformed
input, `-2` `dstCapacity` too small, `-3` missing dictionary
api : lz4frame compression accepts any `dstCapacity`, and only fails if the
output doesn't fit
api : removed from headers : functions deprecated since v1.7.x / v1.8.0
(still exported by liblz4), unprefixed lz4frame enums ; `LZ4_resetStream()`
and `LZ4_resetStreamHC()` are deprecated
api : `LZ4F_compressOptions_t` must be zero-initialized ; reserved fields
are scalars (flatten positional initializers) ; `LZ4F_uncompressedUpdate()`
deprecated (use `.uncompressed`)
api : custom allocators for lz4file (`_advanced()` functions),
`LZ4_USER_MEMORY_FUNCTIONS` also for lz4frame and lz4file ;
`LZ4F_cctx_size()` and `LZ4F_dctx_size()` by @felixhandte
api : HC states include the buffer of levels 10+ (+64 KB per state) : no
allocation during compression
cli : multithreaded compression relies on liblz4 : same output with any nb
of threads and without multithreading support ; `-T#` within a memory budget
(`--memory=#`) ; new `--single-thread`
cli : decodes Firefox's mozlz4 files, proposed by @UnitedMarsupials, and
legacy frames with the Linux kernel end marker, requested by @benjarobin
(frame format documentation by @Artoria2e5)
cli : safer file handling : an output identical to the input is refused, a
source modified during compression is detected, `--rm` keeps the source
after failures, by @Furan666, @Nexory and @immanuwell
cli : benchmark (`-b`) measures frames, compressed as `lz4` does with the
same options
cli : various fixes (`--list`, legacy format, benchmark, `-t -m`, numeric
arguments), by @tansy, @jmestwa-coder, @akashdeshmukh-git, @arshsmith1,
@jlee303 and @Nexory
build: dynamic library multithreaded by default, static library
single-threaded ; cmake `lz4` multithreaded
build: cmake : exported `lz4::lz4` target by @dg0yt, CMake 4 support by
@GeorgH93, `CMAKE_POSITION_INDEPENDENT_CODE` by @ds-sloth
build: cmake : as a subproject, the `lz4` program is no longer built by
default (`-DLZ4_BUILD_CLI=ON` restores it), by @crueter
build: reproducible static library by @rpurdie, AIX support by @shubhamhii,
meson fixes by @grobian, @bgilbert and @eli-schwartz, other fixes by
@hotschmoe, @iwamatsu, @doraorak, @JCash and @brainy
port : RISC-V with `Zicclsm` uses unaligned memory accesses, by @Polaris-911
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
config/rootfiles/common/lz4 | 2 +-
lfs/lz4 | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/config/rootfiles/common/lz4 b/config/rootfiles/common/lz4
index 795207c1a..d73e5663c 100644
--- a/config/rootfiles/common/lz4
+++ b/config/rootfiles/common/lz4
@@ -10,7 +10,7 @@ usr/bin/lz4
#usr/lib/liblz4.a
#usr/lib/liblz4.so
usr/lib/liblz4.so.1
-usr/lib/liblz4.so.1.10.0
+usr/lib/liblz4.so.1.11.1
#usr/lib/pkgconfig/liblz4.pc
#usr/share/man/man1/lz4.1
#usr/share/man/man1/lz4c.1
diff --git a/lfs/lz4 b/lfs/lz4
index cd7488778..1cb4fb1fd 100644
--- a/lfs/lz4
+++ b/lfs/lz4
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2024 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2007-2026 IPFire Team <info@ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 1.10.0
+VER = 1.11.1
THISAPP = lz4-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -41,7 +41,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = c87a939b748b0449e4f1869579ebc109704aa89e8699b6029217f6786c351d1b0329580dd3a955fe509efb113f29aecbafc83084d65d153f5d43610f4840a819
+$(DL_FILE)_BLAKE2 = ff75a065c2e088cdef33608342ac31b892f8b3397a8474f5970c38b1b95035136ba7f4cea2b757cc04a737e6292ada2a36aeb69cd43da67af7d45443dfe0a5ae
install : $(TARGET)
--
2.56.1
next prev parent reply other threads:[~2026-11-12 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 17:04 [PATCH] core207: Ship libssh Adolf Belka
2026-11-12 17:04 ` [PATCH] core207: Ship lz4 Adolf Belka
2026-11-12 17:04 ` [PATCH] core207: Ship ppp Adolf Belka
2026-11-12 17:04 ` [PATCH] libssh: Update to version 0.12.2 Adolf Belka
2026-11-12 17:04 ` Adolf Belka [this message]
2026-11-12 17:04 ` [PATCH] ppp: Update to version 2.5.5 Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261112170458.2062476-5-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox