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.19-rc5, part 2
Date: Fri,  9 Jan 2026 17:40:05 +0100	[thread overview]
Message-ID: <cover.1767974557.git.dsterba@suse.com> (raw)

Hi,

second batch of patches after the EOY break. Please pull, thanks.

- fix potential NULL pointer dereference when replaying tree log after
  an error

- release path before initializing extent tree to avoid potential
  deadlock when allocating new inode

- on filesystems with block size > page size
  - fix potential read out of bounds during encoded read of an inline
    extent
  - only enforce free space tree if v1 cache is required

- print correct tree id in error message

----------------------------------------------------------------
The following changes since commit c1c050f92d8f6aac4e17f7f2230160794fceef0c:

  btrfs: fix reservation leak in some error paths when inserting inline extent (2025-12-16 22:53:15 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 2bb83bc42be6280d9bc363b8fbcd6fdab690d16d:

  btrfs: show correct warning if can't read data reloc tree (2026-01-06 01:23:00 +0100)

----------------------------------------------------------------
Filipe Manana (1):
      btrfs: release path before initializing extent tree in btrfs_read_locked_inode()

Mark Harmstone (1):
      btrfs: show correct warning if can't read data reloc tree

Qu Wenruo (3):
      btrfs: avoid access-beyond-folio for bs > ps encoded writes
      btrfs: only enforce free space tree if v1 cache is required for bs < ps cases
      btrfs: force free space tree for bs > ps cases

Suchit Karunakaran (1):
      btrfs: fix NULL pointer dereference in do_abort_log_replay()

 fs/btrfs/disk-io.c  |  1 +
 fs/btrfs/inode.c    | 41 ++++++++++++++++++++++++++++++++---------
 fs/btrfs/super.c    | 12 +++++-------
 fs/btrfs/tree-log.c |  2 +-
 4 files changed, 39 insertions(+), 17 deletions(-)

             reply	other threads:[~2026-01-09 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 16:40 David Sterba [this message]
2026-01-09 17:06 ` [GIT PULL] Btrfs fixes for 6.19-rc5, part 2 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.1767974557.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.