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 <hongbohbli@tencent.com>
Subject: [GIT PULL] erofs fixes for 7.2-rc6
Date: Mon, 27 Jul 2026 23:33:12 +0800 [thread overview]
Message-ID: <amd6OALSzdFYQOb2@debian> (raw)
Hi Linus,
Could you consider these fixes for 7.2-rc6?
One patch fixes a new regression in page cache sharing introduced
in 7.2-rc3, which can cause a NULL pointer dereference; another
patch limits LZMA stream memory usage on systems with many CPUs.
Thanks,
Gao Xiang
The following changes since commit 1590cf0329716306e948a8fc29f1d3ee87d3989f:
Linux 7.2-rc4 (2026-07-19 13:54:41 -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-rc6-fixes
for you to fetch changes up to c9b47e6b23114e939b17f818471c7a46e59006e7:
erofs: cap LZMA stream pool size (2026-07-27 12:31:11 +0800)
----------------------------------------------------------------
Changes since the last update:
- Keep a valid f_path for page cache sharing to fix a recent mincore()
NULL pointer dereference
- Limit LZMA stream pool size when too many processors are available
- Sync up with Hongbo Li's latest email address
----------------------------------------------------------------
Gao Xiang (1):
erofs: ensure valid f_path for page cache sharing
Hongbo Li (1):
MAINTAINERS: update Hongbo Li's email address
Michael Bommarito (1):
erofs: cap LZMA stream pool size
MAINTAINERS | 2 +-
fs/erofs/Kconfig | 15 ++++++++++++
fs/erofs/decompressor_lzma.c | 3 ++-
fs/erofs/internal.h | 4 +--
fs/erofs/ishare.c | 58 +++++++++++++++++++++-----------------------
5 files changed, 48 insertions(+), 34 deletions(-)
next reply other threads:[~2026-07-27 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 15:33 Gao Xiang [this message]
2026-07-27 21:50 ` [GIT PULL] erofs fixes for 7.2-rc6 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=amd6OALSzdFYQOb2@debian \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=hongbohbli@tencent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox