All of lore.kernel.org
 help / color / mirror / Atom feed
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: don't finish zones if it's not open
Date: Mon, 12 Aug 2024 19:53:27 +0000	[thread overview]
Message-ID: <ZrpoNyb8h0ccIZdF@google.com> (raw)
In-Reply-To: <CACOAw_w0Dyn4T-r00=XrvGO0ZvWCVPv9wPQis9mz-9NXoqwmPA@mail.gmail.com>

On 08/12, Daeho Jeong wrote:
> On Thu, Aug 8, 2024 at 1:59 PM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > Should finish zones if they are open.
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> > ---
> >  include/f2fs_fs.h   | 2 ++
> >  lib/libf2fs_zoned.c | 5 +++--
> >  2 files changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/include/f2fs_fs.h b/include/f2fs_fs.h
> > index 3f5583d18329..15a1c82ae18f 100644
> > --- a/include/f2fs_fs.h
> > +++ b/include/f2fs_fs.h
> > @@ -1742,6 +1742,8 @@ blk_zone_cond_str(struct blk_zone *blkz)
> >   * Handle kernel zone capacity support
> >   */
> >  #define blk_zone_empty(z)      (blk_zone_cond(z) == BLK_ZONE_COND_EMPTY)
> > +#define blk_zone_open(z)       (blk_zone_cond(z) == BLK_ZONE_COND_IMP_OPEN ||  \
> > +                                blk_zone_cond(z) == BLK_ZONE_COND_EXP_OPEN)
> >  #define blk_zone_sector(z)     (z)->start
> >  #define blk_zone_length(z)     (z)->len
> >  #define blk_zone_wp_sector(z)  (z)->wp
> > diff --git a/lib/libf2fs_zoned.c b/lib/libf2fs_zoned.c
> > index 221d7d1337c7..89ba5ad73a76 100644
> > --- a/lib/libf2fs_zoned.c
> > +++ b/lib/libf2fs_zoned.c
> > @@ -513,7 +513,7 @@ int f2fs_finish_zone(int i, void *blkzone)
> >         struct blk_zone_range range;
> >         int ret;
> >
> > -       if (!blk_zone_seq(blkz) || blk_zone_empty(blkz))
> > +       if (!blk_zone_seq(blkz) || !blk_zone_open(blkz))
> 
> Don't we need to check blk_zone_empty() anymore?

I think the purpose of finishing a zone is to close any open zones. I expect
the empty|full zone will be reset by f2fs later before use.

> 
> >                 return 0;
> >
> >         /* Non empty sequential zone: finish */
> > @@ -522,7 +522,8 @@ int f2fs_finish_zone(int i, void *blkzone)
> >         ret = ioctl(dev->fd, BLKFINISHZONE, &range);
> >         if (ret != 0) {
> >                 ret = -errno;
> > -               ERR_MSG("ioctl BLKFINISHZONE failed: errno=%d\n", errno);
> > +               ERR_MSG("ioctl BLKFINISHZONE failed: errno=%d, status=%s\n",
> > +                       errno, blk_zone_cond_str(blkz));
> >         }
> >
> >         return ret;
> > --
> > 2.46.0.76.ge559c4bf1a-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

  reply	other threads:[~2024-08-12 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 20:57 [f2fs-dev] [PATCH] fsck.f2fs: don't finish zones if it's not open Jaegeuk Kim
2024-08-12 18:30 ` Daeho Jeong
2024-08-12 19:53   ` Jaegeuk Kim [this message]
2024-08-13 17:34     ` Daeho Jeong
2024-08-15  0:54 ` Chao Yu

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=ZrpoNyb8h0ccIZdF@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.