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>
Subject: [GIT PULL] erofs fixes for 7.1-rc1
Date: Wed, 22 Apr 2026 02:11:34 +0800 [thread overview]
Message-ID: <aee91ucT5PLdydIC@debian> (raw)
Hi Linus,
Could you consider these three fixes as the following
updates for 7.1-rc1?
They are all small random fixes, but we tend to address them
right now given our priority on crafted images, for example.
Thanks,
Gao Xiang
The following changes since commit a5242d37c83abe86df95c6941e2ace9f9055ffcb:
erofs: error out obviously illegal extents in advance (2026-04-10 16:53:39 +0800)
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-fixes
for you to fetch changes up to 2d8c7edcb661812249469f4a5b62e9339118846f:
erofs: unify lcn as u64 for 32-bit platforms (2026-04-21 16:56:08 +0800)
----------------------------------------------------------------
Changes since the last update:
- Fix dirent nameoff handling to avoid out-of-bound reads
out of crafted images
- Fix two type truncation issues on 32-bit platforms
----------------------------------------------------------------
Gao Xiang (3):
erofs: fix the out-of-bounds nameoff handling for trailing dirents
erofs: fix offset truncation when shifting pgoff on 32-bit platforms
erofs: unify lcn as u64 for 32-bit platforms
fs/erofs/data.c | 2 +-
fs/erofs/dir.c | 28 +++++++++++++++-------------
fs/erofs/zdata.c | 2 +-
fs/erofs/zmap.c | 19 +++++++++----------
4 files changed, 26 insertions(+), 25 deletions(-)
next reply other threads:[~2026-04-21 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 18:11 Gao Xiang [this message]
2026-04-21 18:50 ` [GIT PULL] erofs fixes 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=aee91ucT5PLdydIC@debian \
--to=xiang@kernel.org \
--cc=chao@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