From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] fsck.f2fs: run full scan if checkpoint is disabled
Date: Mon, 4 Dec 2023 17:16:06 -0800 [thread overview]
Message-ID: <ZW551kua2GX0GcIY@google.com> (raw)
In-Reply-To: <CACOAw_zQ8X=HWbX+oiQUeQ0dM7zYJgwTfqWJ6rMBa8rykctJaw@mail.gmail.com>
Thanks. Let me add reviewed-by. :)
On 12/04, Daeho Jeong wrote:
> LGTM
>
> On Mon, Dec 4, 2023 at 10:07 AM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > Let's fix any inconsistency until checkpint being enabled back.
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> > ---
> > fsck/mount.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/fsck/mount.c b/fsck/mount.c
> > index e957904494ef..30c62280b281 100644
> > --- a/fsck/mount.c
> > +++ b/fsck/mount.c
> > @@ -1435,6 +1435,7 @@ static int f2fs_should_proceed(struct f2fs_super_block *sb, u32 flag)
> > {
> > if (!c.fix_on && (c.auto_fix || c.preen_mode)) {
> > if (flag & CP_FSCK_FLAG ||
> > + flag & CP_DISABLED_FLAG ||
> > flag & CP_QUOTA_NEED_FSCK_FLAG ||
> > c.abnormal_stop || c.fs_errors ||
> > (exist_qf_ino(sb) && (flag & CP_ERROR_FLAG))) {
> > --
> > 2.43.0.rc2.451.g8631bc7472-goog
> >
> >
> >
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
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:[~2023-12-05 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 18:05 [f2fs-dev] [PATCH] fsck.f2fs: run full scan if checkpoint is disabled Jaegeuk Kim
2023-12-04 19:12 ` Daeho Jeong
2023-12-05 1:16 ` Jaegeuk Kim [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=ZW551kua2GX0GcIY@google.com \
--to=jaegeuk@kernel.org \
--cc=daeho43@gmail.com \
--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).