linux-btrfs.vger.kernel.org archive mirror
 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.12-rc2
Date: Fri,  4 Oct 2024 16:37:13 +0200	[thread overview]
Message-ID: <cover.1728050979.git.dsterba@suse.com> (raw)

Hi,

please pull the following fixes, thanks.

- in incremental send, fix invalid clone operation for file that got its
  size decreased

- fix __counted_by() annotation of send path cache entries, we don not
  store the terminating NUL

- fix a longstanding bug in relocation (and quite hard to hit by
  chance), drop back reference cache that can get out of sync after
  transaction commit

- wait for fixup worker kthread before finishing umount

- add missing raid-stripe-tree extent for NOCOW files, zoned mode
  cannot have NOCOW files but RST is meant to be a standalone feature

- handle transaction start error during relocation, avoid potential NULL
  pointer dereference of relocation control structure (reported by syzbot)

- disable module-wide rate limiting of debug level messages

- minor fix to tracepoint definition (reported by checkpatch.pl)

----------------------------------------------------------------
The following changes since commit 7f1b63f981b8284c6d8238cb49b5cb156d9a833e:

  btrfs: fix use-after-free on rbtree that tracks inodes for auto defrag (2024-09-17 17:35:53 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.12-rc1-tag

for you to fetch changes up to d6e7ac65d4c106149d08a0ffba39fc516ae3d21b:

  btrfs: disable rate limiting when debug enabled (2024-10-01 19:29:41 +0200)

----------------------------------------------------------------
Filipe Manana (4):
      btrfs: send: fix buffer overflow detection when copying path to cache entry
      btrfs: tracepoints: end assignment with semicolon at btrfs_qgroup_extent event class
      btrfs: send: fix invalid clone operation for file that got its size decreased
      btrfs: wait for fixup workers before stopping cleaner kthread during umount

Johannes Thumshirn (1):
      btrfs: also add stripe entries for NOCOW writes

Josef Bacik (1):
      btrfs: drop the backref cache during relocation if we commit

Leo Martins (1):
      btrfs: disable rate limiting when debug enabled

Qu Wenruo (1):
      btrfs: fix a NULL pointer dereference when failed to start a new trasacntion

 fs/btrfs/backref.c           | 12 ++++---
 fs/btrfs/disk-io.c           | 11 +++++++
 fs/btrfs/inode.c             |  5 +++
 fs/btrfs/messages.c          |  3 +-
 fs/btrfs/relocation.c        | 77 +++-----------------------------------------
 fs/btrfs/send.c              | 31 +++++++++++++++---
 include/trace/events/btrfs.h |  2 +-
 7 files changed, 58 insertions(+), 83 deletions(-)

             reply	other threads:[~2024-10-04 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 14:37 David Sterba [this message]
2024-10-04 17:50 ` [GIT PULL] Btrfs fixes for 6.12-rc2 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.1728050979.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;
as well as URLs for NNTP newsgroup(s).