Linux-f2fs-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: fengnan chang <fengnanchang@gmail.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix hungtask when decompressed fail
Date: Tue, 1 Nov 2022 20:18:56 -0700	[thread overview]
Message-ID: <Y2HhoBnocFff1WFB@sol.localdomain> (raw)
In-Reply-To: <694663F8-701D-4318-94D0-A1F532DDF6F9@gmail.com>

On Wed, Nov 02, 2022 at 11:06:17AM +0800, fengnan chang wrote:
> 
> 
> > 2022年11月2日 10:05,Eric Biggers <ebiggers@kernel.org> 写道:
> > 
> > On Wed, Jun 08, 2022 at 09:48:52PM +0800, 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>
> > 
> > This commit message only explains the problem, not the solution.  It should
> > explain the solution too.
> > 
> > Also, if it's fixing a bug, it needs 'Fixes' and 'Cc stable' tags.
> 
> I’ll add more explanation and tags, thanks.
> 
> > 
> >> diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
> >> index 24824cd96f36..1764e3859262 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;
> >> +			retry_count--;
> >> +			if (PageError(page) && !retry_count) {
> >> +				ret = -EIO;
> >> +				goto out;
> >> +			} else
> > 
> > What is the purpose of using PG_error here?
> 
> In this version, we set PG_error when compressed failed, so check PG_error here.
> Maybe we can remove PG_error in later?
> 

Read I/O errors can be detected via PG_uptodate not being set.  There shouldn't
be any need for PG_error here.

- Eric


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

  reply	other threads:[~2022-11-02  3:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 13:48 [f2fs-dev] [PATCH v2] f2fs: fix hungtask when decompressed fail Fengnan Chang
2022-10-14  8:46 ` fengnan chang
2022-11-01  9:41   ` fengnan chang
2022-11-01 15:06     ` Chao Yu
2022-11-02  2:05 ` Eric Biggers
2022-11-02  3:06   ` fengnan chang
2022-11-02  3:18     ` Eric Biggers [this message]
2022-11-02  3:43       ` fengnan chang
2022-11-02  3:48         ` Eric Biggers

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=Y2HhoBnocFff1WFB@sol.localdomain \
    --to=ebiggers@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