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>,
Binglei Wang <l3b2w1@gmail.com>,
Giuseppe Scrivano <giuseppe@scrivano.org>,
Chao Yu <chao@kernel.org>, Jingbo Xu <jefflexu@163.com>,
Gyokhan Kochmarla <gyokhan@amazon.de>,
Christian Brauner <brauner@kernel.org>
Subject: [GIT PULL] erofs updates for 7.4-rc1
Date: Mon, 19 Oct 2026 22:10:41 +0200 [thread overview]
Message-ID: <atZ5QThkCK8UnB28@XiangdeMacBook-Pro.local> (raw)
Hi Linus,
Could consider these commits for 7.4-rc1?
The most notable change is to support superblock sharing for composefs,
thanks to Giuseppe again: it needs a vfs change, which already goes
through vfs tree [1] so I merge the corresponding vfs branch.
Another one switches to iomap for file-backed mounts on unencoded inodes,
which enables efficient sub-folio I/Os. The others are all random ones.
All commits have been in -next and no potential merge conflict is
observed.
Thanks,
Gao Xiang
[1] https://lore.kernel.org/r/20261016-vfs-7.4-rc1.shared.super-9c2de4415e8b@brauner
The following changes since commit a90ee4305c4a5df72c11b31dacfdc76e00fcf78a:
Linux 7.3-rc6 (2026-10-04 13:45:25 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-7.4-rc1
for you to fetch changes up to 1137aa577a35e2684e8046c3e53f920e79c7cc60:
erofs: enable iomap for file-backed mounts on unencoded inodes (2026-10-17 17:29:36 +0200)
----------------------------------------------------------------
Changes since last update:
- Support superblock sharing for file-backed mounts
- Use iomap for file-backed mounts on unencoded inodes
- Minor fixes and cleanups
----------------------------------------------------------------
Binglei Wang (1):
erofs: fix xattrs handling when metadata compression is used
Chao Yu (1):
MAINTAINERS: erofs: add dev branch to git tree entry
Christian Brauner (1):
Merge patch "erofs: share the superblock for file-backed mounts"
Gao Xiang (3):
Merge branch 'vfs-7.4.shared.super' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
mailmap: update entry for Gao Xiang
erofs: enable iomap for file-backed mounts on unencoded inodes
Giuseppe Scrivano (2):
fs: rename vfs_get_super() to get_tree_super() and export it
erofs: reuse superblock for file-backed mounts
Gyokhan Kochmarla (1):
erofs: use on-disk blkszbits for lz4 max pcluster bound
Jingbo Xu (1):
MAINTAINERS: erofs: update my email address
.mailmap | 1 +
Documentation/filesystems/erofs.rst | 7 ++
MAINTAINERS | 4 +-
fs/erofs/data.c | 34 ++++----
fs/erofs/decompressor.c | 2 +-
fs/erofs/fileio.c | 157 +++++++++++-------------------------
fs/erofs/internal.h | 12 ++-
fs/erofs/ishare.c | 4 +-
fs/erofs/super.c | 56 ++++++++++++-
fs/super.c | 19 ++++-
include/linux/fs_context.h | 4 +
11 files changed, 161 insertions(+), 139 deletions(-)
next reply other threads:[~2026-10-19 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 20:10 Gao Xiang [this message]
2026-10-21 3:03 ` [GIT PULL] erofs updates for 7.4-rc1 pr-tracker-bot
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=atZ5QThkCK8UnB28@XiangdeMacBook-Pro.local \
--to=xiang@kernel.org \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=giuseppe@scrivano.org \
--cc=gyokhan@amazon.de \
--cc=jefflexu@163.com \
--cc=l3b2w1@gmail.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.