All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naohiro Aota <naohiro.aota@wdc.com>
To: linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Cc: Naohiro Aota <naohiro.aota@wdc.com>
Subject: [PATCH STABLE 5.18 v2 0/3] btrfs: backport zoned mode fixes
Date: Mon,  8 Aug 2022 11:01:58 +0900	[thread overview]
Message-ID: <20220808020201.712924-1-naohiro.aota@wdc.com> (raw)

These patches are backport for the 5.18 branch.

They all fixes zoned mode related issued on btrfs.

The patch 3 looks different from upstream commit b3a3b0255797 ("btrfs:
zoned: drop optimization of zone finish") as a refactoring patch is not
picked into the stable branch. But, essentially, they do the same thing
which always zone finish the zones after (nearly) full write.

The v2 just amend a line to add a missing variable declaration.

Naohiro Aota (3):
  btrfs: zoned: prevent allocation from previous data relocation BG
  btrfs: zoned: fix critical section of relocation inode writeback
  btrfs: zoned: drop optimization of zone finish

 fs/btrfs/block-group.h |  1 +
 fs/btrfs/extent-tree.c | 20 +++++++++++++++--
 fs/btrfs/extent_io.c   |  3 ++-
 fs/btrfs/inode.c       |  2 ++
 fs/btrfs/zoned.c       | 50 +++++++++++++++++++++++++++++++++++++-----
 fs/btrfs/zoned.h       |  5 +++++
 6 files changed, 73 insertions(+), 8 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-08-08  2:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08  2:01 Naohiro Aota [this message]
2022-08-08  2:01 ` [PATCH STABLE 5.18 v2 1/3] btrfs: zoned: prevent allocation from previous data relocation BG Naohiro Aota
2022-08-08  2:02 ` [PATCH STABLE 5.18 v2 2/3] btrfs: zoned: fix critical section of relocation inode writeback Naohiro Aota
2022-08-08  2:02 ` [PATCH STABLE 5.18 v2 3/3] btrfs: zoned: drop optimization of zone finish Naohiro Aota
2022-08-08 13:41 ` [PATCH STABLE 5.18 v2 0/3] btrfs: backport zoned mode fixes Greg KH

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=20220808020201.712924-1-naohiro.aota@wdc.com \
    --to=naohiro.aota@wdc.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stable@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 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.