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>,
Junbeom Yeom <junbeom.yeom@samsung.com>
Subject: [GIT PULL] erofs fix for 6.19-rc3
Date: Tue, 23 Dec 2025 22:49:07 +0800 [thread overview]
Message-ID: <aUqr46Y+AqmkowXu@debian> (raw)
Hi Linus,
Could you consider this fix for 6.19-rc3?
Junbeom reported that synchronous reads could hit unintended EIOs
under memory pressure due to incorrect error propagation in
z_erofs_decompress_queue(), where earlier physical clusters in
the same decompression queue may be served for another readahead.
This patch addresses the issue by decompressing each physical cluster
independently as long as disk I/Os succeed, rather than being impacted
by the error status of previous physical clusters in the same queue.
Happy Xmas and new year in advance!
Thanks,
Gao Xiang
The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.19-rc3-fixes
for you to fetch changes up to 4012d78562193ef5eb613bad4b0c0fa187637cfe:
erofs: fix unexpected EIO under memory pressure (2025-12-22 00:18:53 +0800)
----------------------------------------------------------------
Change since last update:
- Fix unexpected EIOs under memory pressure caused by recent
incorrect error propagation logic
----------------------------------------------------------------
Junbeom Yeom (1):
erofs: fix unexpected EIO under memory pressure
fs/erofs/zdata.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2025-12-23 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 14:49 Gao Xiang [this message]
2025-12-24 18:55 ` [GIT PULL] erofs fix for 6.19-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=aUqr46Y+AqmkowXu@debian \
--to=xiang@kernel.org \
--cc=junbeom.yeom@samsung.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