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.2-rc4
Date: Tue, 14 Jul 2026 07:00:53 +0200	[thread overview]
Message-ID: <cover.1784004728.git.dsterba@suse.com> (raw)

Hi,

please pull a few fixes. Thanks.

- fix root structure leak after relocation error

- fix optimization when checksums are read from commit root, fall back
  to checksum root during relocation

- in tree-checker, validate length of inode reference in items

- validate properties before setting them

- validate free space cache entries on load

- transaction abort fixes

- fix printing of internal trees as signed numbers

- add error messages after critical lzo compression errors

----------------------------------------------------------------
The following changes since commit ae2eb64bfd9762536f60b690840adcdf622cdcce:

  btrfs: fix use-after-free after relocation failure with concurrent COW (2026-06-09 18:22:47 +0200)

are available in the Git repository at:

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

for you to fetch changes up to c0041b502e579a5c52e5cae918b90678f03faddd:

  btrfs: print-tree: print header owner as signed (2026-06-30 02:02:03 +0200)

----------------------------------------------------------------
Boris Burkov (1):
      btrfs: fallback to transaction csum tree on a commit root csum miss

Filipe Manana (3):
      btrfs: validate properties before setting them
      btrfs: fix transaction abort logic in btrfs_fileattr_set()
      btrfs: fix root leak if its reloc root is unexpected in merge_reloc_roots()

Johannes Thumshirn (1):
      btrfs: decentralize transaction aborts in create_reloc_root()

Qu Wenruo (2):
      btrfs: lzo: add error message for invalid headers
      btrfs: print-tree: print header owner as signed

Weiming Shi (1):
      btrfs: tree-checker: validate INODE_REF's namelen

Xiang Mei (1):
      btrfs: reject free space cache with more entries than pages

 fs/btrfs/file-item.c        | 26 +++++++++++++++++++++++++-
 fs/btrfs/free-space-cache.c |  3 +++
 fs/btrfs/ioctl.c            | 18 ++++++++++++------
 fs/btrfs/lzo.c              | 15 ++++++++++++---
 fs/btrfs/print-tree.c       |  8 ++++----
 fs/btrfs/props.c            | 16 +++++++++++++---
 fs/btrfs/relocation.c       | 15 +++++++--------
 fs/btrfs/tree-checker.c     |  6 ++++++
 8 files changed, 82 insertions(+), 25 deletions(-)

                 reply	other threads:[~2026-07-14  5:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.1784004728.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.