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 fro 6.18-rc6
Date: Tue, 11 Nov 2025 10:22:35 +0100	[thread overview]
Message-ID: <cover.1762852601.git.dsterba@suse.com> (raw)

Hi,

please pull a few more fixes, thanks.

- fix new inode name tracking in tree-llog

- fix conventional zone and stripe calculations in zoned mode

- fix bio reference counts on error paths in relocation and scrub

----------------------------------------------------------------
The following changes since commit 3b1a4a59a2086badab391687a6a0b86e03048393:

  btrfs: mark dirty extent range for out of bound prealloc extents (2025-10-30 19:18:18 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.18-rc5-tag

for you to fetch changes up to c367af440e03eba7beb0c9f3fe540f9bcb69134a:

  btrfs: release root after error in data_reloc_print_warning_inode() (2025-11-05 20:01:12 +0100)

----------------------------------------------------------------
Filipe Manana (1):
      btrfs: do not update last_log_commit when logging inode due to a new name

Naohiro Aota (2):
      btrfs: zoned: fix conventional zone capacity calculation
      btrfs: zoned: fix stripe width calculation

Zilin Guan (2):
      btrfs: scrub: put bio after errors in scrub_raid56_parity_stripe()
      btrfs: release root after error in data_reloc_print_warning_inode()

 fs/btrfs/inode.c    |  4 +++-
 fs/btrfs/scrub.c    |  2 ++
 fs/btrfs/tree-log.c |  2 +-
 fs/btrfs/zoned.c    | 60 +++++++++++++++++++++++++----------------------------
 4 files changed, 34 insertions(+), 34 deletions(-)

             reply	other threads:[~2025-11-11  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-11  9:22 David Sterba [this message]
2025-11-11 19:10 ` [GIT PULL] Btrfs fixes fro 6.18-rc6 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.1762852601.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.