From: Chao Yu <chao@kernel.org>
To: Weichao Guo <guoweichao@oppo.com>, jaegeuk@kernel.org
Cc: omega@oppo.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: set SBI_NEED_FSCK flag when inconsistent node block found
Date: Sun, 19 Sep 2021 06:34:39 +0800 [thread overview]
Message-ID: <d52c8848-f2d0-c5a4-17f1-8e88285856e3@kernel.org> (raw)
In-Reply-To: <1631969196-341-1-git-send-email-guoweichao@oppo.com>
On 2021/9/18 20:46, Weichao Guo wrote:
> Inconsistent node block will cause a file fail to open or read,
> which could make the user process crashes or stucks. Let's mark
> SBI_NEED_FSCK flag to trigger a fix at next fsck time. After
> unlinking the corrupted file, the user process could regenerate
> a new one and work correctly.
>
> Signed-off-by: Weichao Guo <guoweichao@oppo.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2021-09-18 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 12:46 [f2fs-dev] [PATCH] f2fs: set SBI_NEED_FSCK flag when inconsistent node block found Weichao Guo via Linux-f2fs-devel
2021-09-18 22:34 ` 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=d52c8848-f2d0-c5a4-17f1-8e88285856e3@kernel.org \
--to=chao@kernel.org \
--cc=guoweichao@oppo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=omega@oppo.com \
/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).