public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.0-rc7
Date: Tue, 20 Sep 2022 15:05:42 +0200	[thread overview]
Message-ID: <cover.1663677070.git.dsterba@suse.com> (raw)

Hi,

a few more fixes, also for stable backports. Please pull, thanks.

- two fixes for hangs in the umount sequence where threads depend on
  each other and the work must be finished in the right order

- in zoned mode, wait for flushing all block group metadata IO before
  finishing the zone

----------------------------------------------------------------
The following changes since commit 5da431b71d4b9be3c8cf6786eff9e2d41a5f9f65:

  btrfs: fix the max chunk size and stripe length calculation (2022-09-06 17:49:58 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.0-rc6-tag

for you to fetch changes up to 2dd7e7bc02829eded71be2342a93dc035f5223f9:

  btrfs: zoned: wait for extent buffer IOs before finishing a zone (2022-09-13 14:05:18 +0200)

----------------------------------------------------------------
Filipe Manana (2):
      btrfs: fix hang during unmount when stopping block group reclaim worker
      btrfs: fix hang during unmount when stopping a space reclaim worker

Naohiro Aota (1):
      btrfs: zoned: wait for extent buffer IOs before finishing a zone

 fs/btrfs/disk-io.c | 42 ++++++++++++++++++++++++++++++++++++------
 fs/btrfs/zoned.c   | 40 ++++++++++++++++++++++++++++++++++++++--
 2 files changed, 74 insertions(+), 8 deletions(-)

             reply	other threads:[~2022-09-20 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 13:05 David Sterba [this message]
2022-09-20 17:34 ` [GIT PULL] Btrfs fixes for 6.0-rc7 pr-tracker-bot

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=cover.1663677070.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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