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>, Hongbo Li <lihongbo22@huawei.com>
Subject: [GIT PULL] erofs fixes for 6.18-rc3
Date: Wed, 22 Oct 2025 22:26:25 +0800 [thread overview]
Message-ID: <aPjpkWvwoMrKHxvc@debian> (raw)
Hi Linus,
Could you consider those fixes for 6.18-rc3?
Just three small fixes to address fuzzed images in relatively new
features, as reported by Robert.
Thanks,
Gao Xiang
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.18-rc3-fixes
for you to fetch changes up to 2a13fc417f493e28bdd368785320dd4c2b3d732e:
erofs: consolidate z_erofs_extent_lookback() (2025-10-22 07:54:31 +0800)
----------------------------------------------------------------
Changes since last update:
- Hardening against fuzzed encoded extents
- Fix infinite loops due to crafted subpage compact indexes
- Improve z_erofs_extent_lookback()
----------------------------------------------------------------
Gao Xiang (3):
erofs: fix crafted invalid cases for encoded extents
erofs: avoid infinite loops due to corrupted subpage compact indexes
erofs: consolidate z_erofs_extent_lookback()
fs/erofs/zmap.c | 59 +++++++++++++++++++++++++++++----------------------------
1 file changed, 30 insertions(+), 29 deletions(-)
next reply other threads:[~2025-10-22 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 14:26 Gao Xiang [this message]
2025-10-22 15:17 ` [GIT PULL] erofs fixes for 6.18-rc3 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=aPjpkWvwoMrKHxvc@debian \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=lihongbo22@huawei.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.