linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Daeho Jeong <daeho43@gmail.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/4] f2fs: allocate new section if it's not new
Date: Mon, 4 Dec 2023 10:53:10 -0800	[thread overview]
Message-ID: <CACOAw_x-QMsCyW9Tiw408TSfKXudBnJUJ7Pc3VkRmYQ-vi+eug@mail.gmail.com> (raw)
In-Reply-To: <20231204180428.925779-1-jaegeuk@kernel.org>

LGTM

On Mon, Dec 4, 2023 at 10:06 AM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
>
> If fsck can allocate a new zone, it'd be better to use that instead of
> allocating a new one.
>
> And, it modifies kernel messages.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
>  fs/f2fs/segment.c | 33 +++++++++++++++++----------------
>  1 file changed, 17 insertions(+), 16 deletions(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 08e2f44a1264..9081c9af977a 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -4949,20 +4949,18 @@ static int check_zone_write_pointer(struct f2fs_sb_info *sbi,
>                 return ret;
>         }
>
> -       if (is_set_ckpt_flags(sbi, CP_UMOUNT_FLAG)) {
> -               /*
> -                * If there are valid blocks and the write pointer doesn't match
> -                * with them, we need to report the inconsistency and fill
> -                * the zone till the end to close the zone. This inconsistency
> -                * does not cause write error because the zone will not be
> -                * selected for write operation until it get discarded.
> -                */
> -               f2fs_notice(sbi, "Valid blocks are not aligned with write "
> +       /*
> +        * If there are valid blocks and the write pointer doesn't match
> +        * with them, we need to report the inconsistency and fill
> +        * the zone till the end to close the zone. This inconsistency
> +        * does not cause write error because the zone will not be
> +        * selected for write operation until it get discarded.
> +        */
> +       f2fs_notice(sbi, "Valid blocks are not aligned with write "
>                             "pointer: valid block[0x%x,0x%x] wp[0x%x,0x%x]",
>                             GET_SEGNO(sbi, last_valid_block),
>                             GET_BLKOFF_FROM_SEG0(sbi, last_valid_block),
>                             wp_segno, wp_blkoff);
> -       }
>
>         ret = blkdev_zone_mgmt(fdev->bdev, REQ_OP_ZONE_FINISH,
>                                 zone->start, zone->len, GFP_NOFS);
> @@ -5053,15 +5051,18 @@ static int fix_curseg_write_pointer(struct f2fs_sb_info *sbi, int type)
>                 f2fs_notice(sbi, "Unaligned curseg[%d] with write pointer: "
>                             "curseg[0x%x,0x%x] wp[0x%x,0x%x]", type, cs->segno,
>                             cs->next_blkoff, wp_segno, wp_blkoff);
> -       } else {
> -               f2fs_notice(sbi, "Not successfully unmounted in the previous "
> -                           "mount");
>         }
>
> -       f2fs_notice(sbi, "Assign new section to curseg[%d]: "
> -                   "curseg[0x%x,0x%x]", type, cs->segno, cs->next_blkoff);
> +       /* Allocate a new section if it's not new. */
> +       if (cs->next_blkoff) {
> +               unsigned int old_segno = cs->segno, old_blkoff = cs->next_blkoff;
>
> -       f2fs_allocate_new_section(sbi, type, true);
> +               f2fs_allocate_new_section(sbi, type, true);
> +               f2fs_notice(sbi, "Assign new section to curseg[%d]: "
> +                               "[0x%x,0x%x] -> [0x%x,0x%x]",
> +                               type, old_segno, old_blkoff,
> +                               cs->segno, cs->next_blkoff);
> +       }
>
>         /* check consistency of the zone curseg pointed to */
>         if (check_zone_write_pointer(sbi, zbd, &zone))
> --
> 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

  parent reply	other threads:[~2023-12-04 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 18:04 [f2fs-dev] [PATCH 1/4] f2fs: allocate new section if it's not new Jaegeuk Kim
2023-12-04 18:04 ` [f2fs-dev] [PATCH 2/4] f2fs: fix write pointers on zoned device after roll forward Jaegeuk Kim
2023-12-04 19:02   ` Daeho Jeong
2023-12-04 18:04 ` [f2fs-dev] [PATCH 3/4] f2fs: check write pointers when checkpoint=disable Jaegeuk Kim
2023-12-04 19:03   ` Daeho Jeong
2023-12-04 18:04 ` [f2fs-dev] [PATCH 4/4] f2fs: let's finish or reset zones all the time Jaegeuk Kim
2023-12-04 19:11   ` Daeho Jeong
2023-12-05 19:29   ` [f2fs-dev] [PATCH 4/4 v2] " Jaegeuk Kim
2023-12-04 18:53 ` Daeho Jeong [this message]
2023-12-14 20:50 ` [f2fs-dev] [PATCH 1/4] f2fs: allocate new section if it's not new patchwork-bot+f2fs

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=CACOAw_x-QMsCyW9Tiw408TSfKXudBnJUJ7Pc3VkRmYQ-vi+eug@mail.gmail.com \
    --to=daeho43@gmail.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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).