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.9-rc8
Date: Mon,  6 May 2024 21:44:39 +0200	[thread overview]
Message-ID: <cover.1715024051.git.dsterba@suse.com> (raw)

Hi,

please pull two more fixes, both have some visible effects on user
space.

- add check if quotas are enabled when passing qgroup inheritance info,
  this affects snapper that could fail to create a snapshot

- do check for leaf/node flag WRITTEN earlier so that nodes are
  completely validated before access, this used to be done by integrity
  checker but it's been removed and left an unhandled case

----------------------------------------------------------------
The following changes since commit 63a6ce5a1a6261e4c70bad2b55c4e0de8da4762e:

  btrfs: set correct ram_bytes when splitting ordered extent (2024-04-30 12:03:44 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.9-rc7-tag

for you to fetch changes up to e03418abde871314e1a3a550f4c8afb7b89cb273:

  btrfs: make sure that WRITTEN is set on all metadata blocks (2024-05-02 22:11:13 +0200)

----------------------------------------------------------------
Josef Bacik (1):
      btrfs: make sure that WRITTEN is set on all metadata blocks

Qu Wenruo (1):
      btrfs: qgroup: do not check qgroup inherit if qgroup is disabled

 fs/btrfs/qgroup.c       |  2 ++
 fs/btrfs/tree-checker.c | 30 +++++++++++++++---------------
 fs/btrfs/tree-checker.h |  1 +
 3 files changed, 18 insertions(+), 15 deletions(-)

             reply	other threads:[~2024-05-06 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 19:44 David Sterba [this message]
2024-05-06 20:46 ` [GIT PULL] Btrfs fixes for 6.9-rc8 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.1715024051.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