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-rc3
Date: Mon, 8 Apr 2024 20:30:02 +0200 [thread overview]
Message-ID: <cover.1712333355.git.dsterba@suse.com> (raw)
Hi,
please pull several fixes to qgroups that have been recently identified
by test generic/475, thanks.
- fix prealloc reserve leak in subvolume operations
- various other fixes in reservation setup, conversion or cleanup
----------------------------------------------------------------
The following changes since commit ef1e68236b9153c27cb7cf29ead0c532870d4215:
btrfs: fix race in read_extent_buffer_pages() (2024-03-26 16:42:39 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.9-rc2-tag
for you to fetch changes up to 6e68de0bb0ed59e0554a0c15ede7308c47351e2d:
btrfs: always clear PERTRANS metadata during commit (2024-04-02 19:19:13 +0200)
----------------------------------------------------------------
Boris Burkov (6):
btrfs: qgroup: correctly model root qgroup rsv in convert
btrfs: qgroup: fix qgroup prealloc rsv leak in subvolume operations
btrfs: record delayed inode root in transaction
btrfs: qgroup: convert PREALLOC to PERTRANS after record_root_in_trans
btrfs: make btrfs_clear_delalloc_extent() free delalloc reserve
btrfs: always clear PERTRANS metadata during commit
fs/btrfs/delayed-inode.c | 3 +++
fs/btrfs/inode.c | 15 +++++++++++++--
fs/btrfs/ioctl.c | 37 ++++++++++++++++++++++++++++---------
fs/btrfs/qgroup.c | 2 ++
fs/btrfs/root-tree.c | 10 ----------
fs/btrfs/root-tree.h | 2 --
fs/btrfs/transaction.c | 19 +++++++++----------
7 files changed, 55 insertions(+), 33 deletions(-)
next reply other threads:[~2024-04-08 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 18:30 David Sterba [this message]
2024-04-08 23:19 ` [GIT PULL] Btrfs fixes for 6.9-rc3 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.1712333355.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.