All of lore.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.9-rc5
Date: Thu, 18 Apr 2024 01:45:43 +0200	[thread overview]
Message-ID: <cover.1713396900.git.dsterba@suse.com> (raw)

Hi,

please pull the following fixes, thanks.

- fixup in zoned mode for out-of-order writes of metadata that are no
  longer necessary, this used to be tracked in a separate list but now
  the old locaion needs to be zeroed out, also add assertions

- fix bulk page allocation retry, this may stall after first failure for
  compression read/write

----------------------------------------------------------------
The following changes since commit 6e68de0bb0ed59e0554a0c15ede7308c47351e2d:

  btrfs: always clear PERTRANS metadata during commit (2024-04-02 19:19:13 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.9-rc4-tag

for you to fetch changes up to 1db7959aacd905e6487d0478ac01d89f86eb1e51:

  btrfs: do not wait for short bulk allocation (2024-04-09 23:20:32 +0200)

----------------------------------------------------------------
Naohiro Aota (2):
      btrfs: zoned: do not flag ZEROOUT on non-dirty extent buffer
      btrfs: zoned: add ASSERT and WARN for EXTENT_BUFFER_ZONED_ZEROOUT handling

Qu Wenruo (1):
      btrfs: do not wait for short bulk allocation

 fs/btrfs/extent-tree.c |  8 ++++++++
 fs/btrfs/extent_io.c   | 21 ++++++---------------
 2 files changed, 14 insertions(+), 15 deletions(-)

             reply	other threads:[~2024-04-17 23:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 23:45 David Sterba [this message]
2024-04-18  0:14 ` [GIT PULL] Btrfs fixes for 6.9-rc5 Linus Torvalds
2024-04-18  0:25   ` David Sterba
2024-04-18  1:30 ` 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.1713396900.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 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.