public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org, torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.15-rc6
Date: Tue,  6 May 2025 16:06:18 +0200	[thread overview]
Message-ID: <cover.1746539430.git.dsterba@suse.com> (raw)

Hi,

a few more fixes, minor updates and one revert. Please pull, thanks.

- revert device path canonicalization, this does not work as intended
  with namespaces and is not reliable in all setups

- fix crash in scrub when checksum tree is not valid, e.g. when mounted
  with rescue=ignoredatacsums

- fix crash when tracepoint btrfs_prelim_ref_insert is enabled

- other minor fixups
  - open code folio_index(), meant to be used in MM code
  - use matching type for sizeof in compression allocation

----------------------------------------------------------------
The following changes since commit e08e49d986f82c30f42ad0ed43ebbede1e1e3739:

  btrfs: adjust subpage bit start based on sectorsize (2025-04-23 08:42:10 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.15-rc5-tag

for you to fetch changes up to 38e541051e1d19e8b1479a6af587a7884653e041:

  btrfs: open code folio_index() in btree_clear_folio_dirty_tag() (2025-05-02 13:20:56 +0200)

----------------------------------------------------------------
Boris Burkov (1):
      btrfs: handle empty eb->folios in num_extent_folios()

Goldwyn Rodrigues (1):
      btrfs: correct the order of prelim_ref arguments in btrfs__prelim_ref

Kairui Song (1):
      btrfs: open code folio_index() in btree_clear_folio_dirty_tag()

Kees Cook (1):
      btrfs: compression: adjust cb->compressed_folios allocation type

Qu Wenruo (2):
      btrfs: avoid NULL pointer dereference if no valid csum tree
      Revert "btrfs: canonicalize the device path before adding it"

 fs/btrfs/compression.c       |  2 +-
 fs/btrfs/extent_io.c         |  4 +-
 fs/btrfs/extent_io.h         |  2 +
 fs/btrfs/scrub.c             |  4 +-
 fs/btrfs/volumes.c           | 91 +-------------------------------------------
 include/trace/events/btrfs.h |  2 +-
 6 files changed, 9 insertions(+), 96 deletions(-)

             reply	other threads:[~2025-05-06 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 14:06 David Sterba [this message]
2025-05-06 16:38 ` [GIT PULL] Btrfs fixes for 6.15-rc6 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2025-03-07 19:58 David Sterba
2025-03-07 22:30 ` 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.1746539430.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