linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Fengnan Chang <fengnanchang@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix hungtask when decompressed fail
Date: Wed, 8 Jun 2022 09:57:03 +0800	[thread overview]
Message-ID: <73fc3d5a-b2c7-194a-82d3-3eb923f96321@kernel.org> (raw)
In-Reply-To: <Yp+cwxXag2ZPbvb8@google.com>

On 2022/6/8 2:45, Jaegeuk Kim wrote:
> On 05/11, Fengnan Chang wrote:
>> When decompressed failed, f2fs_prepare_compress_overwrite will enter
>> endless loop, may casue hungtask.
>>
>> [   14.088665] F2FS-fs (nvme0n1): lz4 decompress failed, ret:-4155
>> [   14.089851] F2FS-fs (nvme0n1): lz4 decompress failed, ret:-4155
>>
>> Signed-off-by: Fengnan Chang <fengnanchang@gmail.com>
>> ---
>>   fs/f2fs/compress.c | 9 +++++++--
>>   1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
>> index 12a56f9e1572..6a65443fd9b3 100644
>> --- a/fs/f2fs/compress.c
>> +++ b/fs/f2fs/compress.c
>> @@ -1060,7 +1060,7 @@ static int prepare_compress_overwrite(struct compress_ctx *cc,
>>   	sector_t last_block_in_bio;
>>   	unsigned fgp_flag = FGP_LOCK | FGP_WRITE | FGP_CREAT;
>>   	pgoff_t start_idx = start_idx_of_cluster(cc);
>> -	int i, ret;
>> +	int i, ret, retry_count = 3;
>>   
>>   retry:
>>   	ret = f2fs_is_compressed_cluster(cc->inode, start_idx);
>> @@ -1120,7 +1120,12 @@ static int prepare_compress_overwrite(struct compress_ctx *cc,
>>   			f2fs_put_rpages(cc);
>>   			f2fs_unlock_rpages(cc, i + 1);
>>   			f2fs_destroy_compress_ctx(cc, true);
>> -			goto retry;
> 
> Do we need to return EIO right away?
> 			if (!page)

page point is valid here, however page is not uptodate here.

Maybe we can set Pg_error flag if decompress failed, and here, we can break the
loop if Pg_error flag was set?

Thanks,

> 				goto retry;
> 			ret = -EIO;
> 			goto out;
> 
>> +			if (retry_count--)
>> +				goto retry;
>> +			else {
>> +				ret = -EIO;
>> +				goto out;
>> +			}
>>   		}
>>   	}
>>   
>> -- 
>> 2.25.1


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2022-06-08  1:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  7:14 [f2fs-dev] [PATCH] f2fs: fix hungtask when decompressed fail Fengnan Chang
2022-06-03  2:12 ` fengnan chang
2022-06-07 18:45 ` Jaegeuk Kim
2022-06-08  1:57   ` 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=73fc3d5a-b2c7-194a-82d3-3eb923f96321@kernel.org \
    --to=chao@kernel.org \
    --cc=fengnanchang@gmail.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).