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 7.4-rc3
Date: Thu, 12 Nov 2026 19:08:57 +0100	[thread overview]
Message-ID: <cover.1794506624.git.dsterba@suse.com> (raw)

Hi,

please pull a few fixes. Thanks.

- zoned mode fixes
  - fix counting active zones after activation
  - redo zone reset after error
  - update device lock range during mount and zone loading to avoid lockdep
    warnings with device drivers (virtio)
  - space accounting and extent buffer handling fixes

- fix keeping zstd workspace for the last level

- in SUBVOL_SYNC ioctl handle a real case of a subvolume with 0 refs

- properly handle case of zero num_stripes when reading chunk items

- exclude reloc tree from xarray as it's special and it's key does not fit
  unsigned long on 32bit platforms

- in tree-checker, handle extent item tree owner depending on the features
  (enabled in simple quota mode)

- fix bio control structure leak when checksumming fails

----------------------------------------------------------------
The following changes since commit 8c66a6aa59a5df1d672d72b7cd379d897ff73200:

  btrfs: zoned: fix double free of bitmaps on clone failure (2026-10-30 23:17:16 +0100)

are available in the Git repository at:

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

for you to fetch changes up to d27d0039bc1334be8a72c769e14c0b0c3efc317d:

  btrfs: fix bio counter and bioc leak when async checksumming fails (2026-11-09 18:50:58 +0100)

----------------------------------------------------------------
Cheng Yongkang (2):
      btrfs: reject refs=0 subvolume without DEAD in SUBVOL_SYNC_WAIT
      btrfs: handle zero num_stripes in btrfs_chunk_item_size()

Filipe Manana (1):
      btrfs: zstd: prevent leak of workspace below maximum level

Johannes Thumshirn (6):
      btrfs: zoned: only change active zone counter on successful (de)activation
      btrfs: zoned: fix possible UAF in wait_eb_writebacks()
      btrfs: zoned: requeue block group if zone reset bails out
      btrfs: zoned: avoid underflow of space info bytes_zone_unusable
      btrfs: zoned: don't wait for ordered extents in do_zone_finish()
      btrfs: zoned: fix lockdep splat on mount

Mani Tofigh (1):
      btrfs: fix bio counter and bioc leak when async checksumming fails

Qu Wenruo (1):
      btrfs: do not insert the data reloc tree into fs_roots_radix

Siddharth Mishra (1):
      btrfs: tree-checker: reject extent owner ref without simple quota

 fs/btrfs/bio.c          |  4 +++
 fs/btrfs/block-group.c  |  2 +-
 fs/btrfs/disk-io.c      | 53 +++++++++++++++++++++++++++------
 fs/btrfs/ioctl.c        |  8 +++--
 fs/btrfs/tree-checker.c |  6 +++-
 fs/btrfs/volumes.h      |  5 ++--
 fs/btrfs/zoned.c        | 78 +++++++++++++++++++++++++++++++++++--------------
 fs/btrfs/zstd.c         |  3 +-
 8 files changed, 120 insertions(+), 39 deletions(-)

             reply	other threads:[~2026-11-12 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 18:08 David Sterba [this message]
2026-11-12 21:24 ` [GIT PULL] Btrfs fixes for 7.4-rc3 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.1794506624.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.