[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210316031515.90954-1-huangjianan@oppo.com>
Date: Tue, 16 Mar 2021 11:15:14 +0800
From: Huang Jianan <huangjianan@...o.com>
To: linux-erofs@...ts.ozlabs.org
Cc: huangjianan@...o.com, guoweichao@...o.com, zhangshiming@...o.com,
linux-kernel@...r.kernel.org, Gao Xiang <hsiangkao@...hat.com>
Subject: [PATCH v6 1/2] erofs: avoid memory allocation failure during rolling decompression
Currently, err would be treated as io error. Therefore, it'd be
better to ensure memory allocation during rolling decompression
to avoid such io error.
In the long term, we might consider adding another !Uptodate case
for such case.
Signed-off-by: Huang Jianan <huangjianan@...o.com>
Signed-off-by: Guo Weichao <guoweichao@...o.com>
Reviewed-by: Gao Xiang <hsiangkao@...hat.com>
---
fs/erofs/decompressor.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/fs/erofs/decompressor.c b/fs/erofs/decompressor.c
index 1cb1ffd10569..34e73ff76f89 100644
--- a/fs/erofs/decompressor.c
+++ b/fs/erofs/decompressor.c
@@ -73,9 +73,8 @@ static int z_erofs_lz4_prepare_destpages(struct z_erofs_decompress_req *rq,
victim = availables[--top];
get_page(victim);
} else {
- victim = erofs_allocpage(pagepool, GFP_KERNEL);
- if (!victim)
- return -ENOMEM;
+ victim = erofs_allocpage(pagepool,
+ GFP_KERNEL | __GFP_NOFAIL);
set_page_private(victim, Z_EROFS_SHORTLIVED_PAGE);
}
rq->out[i] = victim;
--
2.25.1
Powered by blists - more mailing lists