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>
Subject: [GIT PULL] erofs updates for 7.1-rc1
Date: Mon, 13 Apr 2026 12:47:49 +0800 [thread overview]
Message-ID: <adx1dXEp8xyWwgZ2@debian> (raw)
Hi Linus,
Could you consider this pull request for 7.1-rc1?
No outstanding feature for this cycle and there are small random
fixes as below. No potential merge conflict is observed.
Thanks,
Gao Xiang
The following changes since commit 7aaa8047eafd0bd628065b15757d9b48c5f9c07d:
Linux 7.0-rc6 (2026-03-29 15:40:00 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-7.1-rc1
for you to fetch changes up to a5242d37c83abe86df95c6941e2ace9f9055ffcb:
erofs: error out obviously illegal extents in advance (2026-04-10 16:53:39 +0800)
----------------------------------------------------------------
Changes since last update:
- Validate xattr h_shared_count to report -EFSCORRUPTED explicitly
for crafted images
- Verify metadata accesses for file-backed mounts via rw_verify_area()
- Fix FS_IOC_GETFSLABEL to include the trailing NUL byte, consistent
with ext4 and xfs
- Properly handle 48-bit on-disk blocks/uniaddr for extra devices
- Fix an index underflow in the LZ4 in-place decompression that can
cause out-of-bounds accesses with crafted images
- Minor fixes and cleanups
----------------------------------------------------------------
Gao Xiang (3):
erofs: verify metadata accesses for file-backed mounts
erofs: clean up encoded map flags
erofs: error out obviously illegal extents in advance
Junrui Luo (1):
erofs: fix unsigned underflow in z_erofs_lz4_handle_overlap()
Utkal Singh (1):
erofs: harden h_shared_count in erofs_init_inode_xattrs()
Zhan Xusheng (3):
erofs: ensure all folios are managed in erofs_try_to_free_all_cached_folios()
erofs: include the trailing NUL in FS_IOC_GETFSLABEL
erofs: handle 48-bit blocks/uniaddr for extra devices
fs/erofs/data.c | 14 ++++++++++++++
fs/erofs/erofs_fs.h | 4 ++--
fs/erofs/inode.c | 2 +-
fs/erofs/internal.h | 23 +++++++++++------------
fs/erofs/super.c | 8 ++++++--
fs/erofs/xattr.c | 8 ++++++++
fs/erofs/zdata.c | 22 ++++++++++------------
fs/erofs/zmap.c | 43 +++++++++++++++++++++++++------------------
include/trace/events/erofs.h | 7 +++----
9 files changed, 80 insertions(+), 51 deletions(-)
next reply other threads:[~2026-04-13 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 4:47 Gao Xiang [this message]
2026-04-14 0:30 ` [GIT PULL] erofs updates for 7.1-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=adx1dXEp8xyWwgZ2@debian \
--to=xiang@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox