From: Utkal Singh <singhutkal015@gmail.com>
To: hsiangkao@linux.alibaba.com
Cc: linux-erofs@lists.ozlabs.org, Gao Xiang <xiang@kernel.org>
Subject: [PATCH v2] erofs-utils: release 1.9.1
Date: Sun, 15 Mar 2026 14:20:30 +0000 [thread overview]
Message-ID: <20260315142030.2628-1-singhutkal015@gmail.com> (raw)
In-Reply-To: <20260315072806.17504-1-singhutkal015@gmail.com>
From: Gao Xiang <xiang@kernel.org>
Signed-off-by: Gao Xiang <xiang@kernel.org>
---
ChangeLog | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index 8b80850..f47a5e5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,20 @@
+erofs-utils 1.9.1
+
+ * A quick maintenance release includes the following fixes:
+ - (erofsfuse) Synchronize kernel patches to fix encoded extents
+ and shared xattrs in the metabox;
+ - (mkfs.erofs) Do not set LZ4_0PADDING for plain filesystems;
+ - (fsck.erofs) Support extracting subtrees (Inseob Kim);
+ - (mount.erofs) Fix a flag-clearing bug that can cause mount
+ failures (Yifan Zhao);
+ - (mkfs.erofs) Fix a CPU spin when using `--tar=f` if stdin is
+ closed (David Scott);
+ - (mkfs.erofs) Fix crashes in the rebuild mode when the source
+ images contains xattrs (lishixian);
+ - Miscellaneous fixes.
+
+ -- Gao Xiang <xiang@kernel.org> Wed, 04 Mar 2026 00:00:00 +0800
+
erofs-utils 1.9
* This release includes the following updates:
--
2.43.0
next prev parent reply other threads:[~2026-03-15 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 7:28 [PATCH] erofs-utils: lib: validate algorithm format before use in z_erofs_map_blocks_ext Utkal Singh
2026-03-15 10:39 ` Gao Xiang
2026-03-15 14:20 ` Utkal Singh [this message]
2026-03-15 14:22 ` [PATCH v2] erofs-utils: lib: validate algorithm for encoded extents Utkal Singh
2026-03-16 3:11 ` Yifan Zhao
2026-03-16 5:33 ` Utkal Singh
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=20260315142030.2628-1-singhutkal015@gmail.com \
--to=singhutkal015@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=xiang@kernel.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