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 fixes for 6.18-rc5
Date: Tue,  4 Nov 2025 05:57:28 +0100	[thread overview]
Message-ID: <cover.1762230638.git.dsterba@suse.com> (raw)

Hi,

please pull a few more short fixes. Thanks.

- fix memory leak in qgroup relation ioctl when qgroup levels are
  invalid

- don't write back dirty metadata on filesystem with errors

- properly log renamed links

- properly mark prealloc extent range beyond inode size as dirty
  (when no-noles is not enabled)

----------------------------------------------------------------
The following changes since commit ada7d45b568abe4f1fd9c53d66e05fbea300674b:

  btrfs: ref-verify: fix IS_ERR() vs NULL check in btrfs_build_ref_tree() (2025-10-22 09:40:07 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 3b1a4a59a2086badab391687a6a0b86e03048393:

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

----------------------------------------------------------------
Filipe Manana (1):
      btrfs: set inode flag BTRFS_INODE_COPY_EVERYTHING when logging new name

Qu Wenruo (1):
      btrfs: ensure no dirty metadata is written back for an fs with errors

Shardul Bankar (1):
      btrfs: fix memory leak of qgroup_list in btrfs_add_qgroup_relation

austinchang (1):
      btrfs: mark dirty extent range for out of bound prealloc extents

 fs/btrfs/extent_io.c |  8 ++++++++
 fs/btrfs/file.c      | 10 ++++++++++
 fs/btrfs/inode.c     |  1 -
 fs/btrfs/qgroup.c    |  4 +++-
 fs/btrfs/tree-log.c  |  3 +++
 5 files changed, 24 insertions(+), 2 deletions(-)

             reply	other threads:[~2025-11-04  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04  4:57 David Sterba [this message]
2025-11-04  5:45 ` [GIT PULL] Btrfs fixes for 6.18-rc5 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.1762230638.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