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.10-rc6
Date: Thu, 27 Jun 2024 17:28:32 +0200 [thread overview]
Message-ID: <cover.1719501798.git.dsterba@suse.com> (raw)
Hi,
a few more fixes. Please pull, thanks.
- fix quota root leak after quota disable failure
- fix condition when checking if a zone can be added as free
- allocate inode in NOFS context during logging or tree-log replay
- handle raid-stripe-tree lookup correctly during scrub
----------------------------------------------------------------
The following changes since commit cebae292e0c32a228e8f2219c270a7237be24a6a:
btrfs: zoned: allocate dummy checksums for zoned NODATASUM writes (2024-06-13 20:43:55 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.10-rc5-tag
for you to fetch changes up to a7e4c6a3031c74078dba7fa36239d0f4fe476c53:
btrfs: qgroup: fix quota root leak after quota disable failure (2024-06-25 00:35:50 +0200)
----------------------------------------------------------------
Filipe Manana (2):
btrfs: use NOFS context when getting inodes during logging and log replay
btrfs: qgroup: fix quota root leak after quota disable failure
Naohiro Aota (1):
btrfs: zoned: fix initial free space detection
Qu Wenruo (1):
btrfs: scrub: handle RST lookup error correctly
fs/btrfs/free-space-cache.c | 2 +-
fs/btrfs/qgroup.c | 4 ++--
fs/btrfs/scrub.c | 26 +++++++++++++++-----------
fs/btrfs/tree-log.c | 43 ++++++++++++++++++++++++++++---------------
4 files changed, 46 insertions(+), 29 deletions(-)
next reply other threads:[~2024-06-27 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 15:28 David Sterba [this message]
2024-06-27 17:34 ` [GIT PULL] Btrfs fixes for 6.10-rc6 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.1719501798.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