From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
Chao Yu <chao@kernel.org>, Zhan Xusheng <zhanxusheng@xiaomi.com>,
Hongbo Li <lihongbo22@huawei.com>,
Jingbo Xu <jefflexu@linux.alibaba.com>
Subject: [GIT PULL] erofs updates for 7.2-rc1
Date: Mon, 22 Jun 2026 23:13:07 +0800 [thread overview]
Message-ID: <ajlRA7jYcsnYPXiw@debian> (raw)
Hi Linus,
Sorry for late email this time, but could you consider these
commits for 7.2-rc1?
The most notable change is the removal of the fscache backend: it
has been deprecated for almost two years, mainly because EROFS
file-backed mounts and fanotify pre-content hooks (together with
erofs-utils) now provide better functionality and simpler codebase.
In addition, fscache has depended on netfslib for years, which is
undesirable for EROFS since it is a local filesystem. More details
are shown in [1].
In addition, sparse support has been added to the pcluster layout,
which is helpful for large sparse AI datasets, and map requests for
chunk-based inodes have been optimized to be more efficient as well.
There are also the usual fixes and cleanups.
All commits have been in -next and no potential merge conflict is
observed.
Thanks,
Gao Xiang
[1] https://lore.kernel.org/r/20260622013622.934174-1-hsiangkao@linux.alibaba.com
The following changes since commit 4549871118cf616eecdd2d939f78e3b9e1dddc48:
Linux 7.1-rc7 (2026-06-07 15:37:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-7.2-rc1
for you to fetch changes up to 803d09a554055aba160a62abd1e4b1260b899dc1:
erofs: handle 48-bit blocks_hi for compressed inodes (2026-06-22 18:50:36 +0800)
----------------------------------------------------------------
Changes since last update:
- Report more consecutive chunks of the same type
for each iomap request
- Add sparse support for the pcluster layout
- Update the EROFS documentation overview
- Remove the deprecated fscache backend
- Various fixes and cleanups
----------------------------------------------------------------
Gao Xiang (7):
erofs: clean up erofs_ishare_fill_inode()
erofs: update the overview of the documentation
erofs: call erofs_exit_ishare() before rcu_barrier()
erofs: introduce erofs_map_chunks()
erofs: add sparse support to pcluster layout
erofs: simplify RCU read critical sections
erofs: remove fscache backend entirely
Zhan Xusheng (2):
erofs: add folio order to trace_erofs_read_folio
erofs: handle 48-bit blocks_hi for compressed inodes
Documentation/filesystems/erofs.rst | 138 ++++----
fs/erofs/Kconfig | 21 +-
fs/erofs/Makefile | 1 -
fs/erofs/data.c | 135 ++++----
fs/erofs/erofs_fs.h | 2 +
fs/erofs/fscache.c | 664 ------------------------------------
fs/erofs/inode.c | 7 +-
fs/erofs/internal.h | 72 +---
fs/erofs/ishare.c | 47 ++-
fs/erofs/super.c | 98 ++----
fs/erofs/zdata.c | 38 +--
fs/erofs/zmap.c | 33 +-
include/trace/events/erofs.h | 9 +-
13 files changed, 231 insertions(+), 1034 deletions(-)
delete mode 100644 fs/erofs/fscache.c
reply other threads:[~2026-06-22 15:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ajlRA7jYcsnYPXiw@debian \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=jefflexu@linux.alibaba.com \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zhanxusheng@xiaomi.com \
/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