Linux Btrfs filesystem development
 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 fixup for 6.16 pull request
Date: Tue, 27 May 2025 13:49:22 +0200	[thread overview]
Message-ID: <cover.1748346039.git.dsterba@suse.com> (raw)

Hi,

please pull a fixup to the xarray conversion sent in the main 6.16
batch. It was not included because it would cause rebase/refresh of like
80 patches, right before sending the early pull request last week.

It's fixing a bug when zoned mode is enabled on btrfs so it's not
affecting most people.

The commit is fresh but the fix has been tested and verified, no reason
to delay it.

Thanks.

----------------------------------------------------------------
The following changes since commit eeb133a6341280a1315c12b5b24a42e1fbf35487:

  btrfs: move misplaced comment of btrfs_path::keep_locks (2025-05-17 21:15:08 +0200)

are available in the Git repository at:

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

for you to fetch changes up to b83825a8f56a34e7352e424aae64ffe6b88247d1:

  btrfs: don't drop a reference if btrfs_check_write_meta_pointer() fails (2025-05-27 13:39:15 +0200)

----------------------------------------------------------------
Josef Bacik (1):
      btrfs: don't drop a reference if btrfs_check_write_meta_pointer() fails

 fs/btrfs/extent_io.c | 1 -
 1 file changed, 1 deletion(-)

             reply	other threads:[~2025-05-27 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 11:49 David Sterba [this message]
2025-05-28 19:44 ` [GIT PULL] Btrfs fixup for 6.16 pull request 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.1748346039.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