mirror of https://lore.kernel.org/lkml/
 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.17-rc7, part 2
Date: Sun, 21 Sep 2025 06:35:41 +0200	[thread overview]
Message-ID: <cover.1758428886.git.dsterba@suse.com> (raw)

Hi,

please pull a few short fixes for btrfs. Thanks.

- in tree-checker, fix wrong size of check for inode ref item

- in ref-verify, handle combination of mount options that allow
  partially damaged extent tree (reported by syzbot)

- additional validation of compression mount option to catch invalid
  string as level

----------------------------------------------------------------
The following changes since commit 80eb65ccf6f72dc37b972583fe71cd8a50ff7e51:

  btrfs: annotate block group access with data_race() when sorting for reclaim (2025-09-15 05:25:43 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.17-rc6-tag

for you to fetch changes up to b98b208300573f4ab29507f81194a6030b208444:

  btrfs: reject invalid compression level (2025-09-18 13:18:49 +0200)

----------------------------------------------------------------
David Sterba (1):
      btrfs: ref-verify: handle damaged extent root tree

Qu Wenruo (2):
      btrfs: tree-checker: fix the incorrect inode ref size check
      btrfs: reject invalid compression level

 fs/btrfs/compression.c  | 22 +++++++++++++---------
 fs/btrfs/compression.h  |  2 +-
 fs/btrfs/ref-verify.c   |  9 ++++++++-
 fs/btrfs/super.c        | 27 +++++++++++++++++++--------
 fs/btrfs/tree-checker.c |  4 ++--
 5 files changed, 43 insertions(+), 21 deletions(-)

             reply	other threads:[~2025-09-21  4:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-21  4:35 David Sterba [this message]
2025-09-21  4:45 ` 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.1758428886.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

all inboxes | Powered by JetHome®