From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: chao@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] erofs: avoid noisy messages for transient -ENOMEM
Date: Thu, 22 Jan 2026 17:03:52 +0800 [thread overview]
Message-ID: <62cc89b9-a70d-4506-826b-28eb4010e372@kernel.org> (raw)
In-Reply-To: <20251226060945.786901-1-hsiangkao@linux.alibaba.com>
On 12/26/2025 2:09 PM, Gao Xiang wrote:
> EROFS may allocate temporary pages using GFP_NOWAIT | GFP_NORETRY
> when pcl->besteffort is off (e.g., for readahead requests).
>
> If the allocation fails, the original request will fall back to
> synchronous read, so the failure is transient.
>
> Such fallback can frequently happen in low memory scenarios, but since
> these failures are expected and temporary, avoid printing error
> messages like below:
>
> [ 7425.184264] erofs (device sr0): failed to decompress (lz4) -ENOMEM @ pa 148447232 size 28672 => 26788
> [ 7426.244267] erofs (device sr0): failed to decompress (lz4) -ENOMEM @ pa 149422080 size 28672 => 15903
> [ 7426.245508] erofs (device sr0): failed to decompress (lz4) -ENOMEM @ pa 138440704 size 28672 => 39294
> ...
> [ 7504.258373] erofs (device sr0): failed to decompress (lz4) -ENOMEM @ pa 93581312 size 20480 => 47366
>
> Fixes: 831faabed812 ("erofs: improve decompression error reporting")
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2026-01-22 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 6:09 Gao Xiang
2026-01-22 9:03 ` Chao Yu [this message]
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=62cc89b9-a70d-4506-826b-28eb4010e372@kernel.org \
--to=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®