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-rc7
Date: Thu, 2 May 2024 14:57:18 +0200 [thread overview]
Message-ID: <cover.1714654371.git.dsterba@suse.com> (raw)
Hi,
please pull a few more fixes, thanks.
- set correct ram_bytes when splitting ordered extent, this is
can be inconsistent on-disk but harmless as it's not used for
calculations and it's only advisory for compression
- fix lockdep splat when taking cleaner mutex in qgroups disable ioctl
- fix missing mutex unlock on error path when looking up sys chunk for
relocation
----------------------------------------------------------------
The following changes since commit fe1c6c7acce10baf9521d6dccc17268d91ee2305:
btrfs: fix wrong block_start calculation for btrfs_drop_extent_map_range() (2024-04-18 18:18:50 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.9-rc6-tag
for you to fetch changes up to 63a6ce5a1a6261e4c70bad2b55c4e0de8da4762e:
btrfs: set correct ram_bytes when splitting ordered extent (2024-04-30 12:03:44 +0200)
----------------------------------------------------------------
Dominique Martinet (1):
btrfs: add missing mutex_unlock in btrfs_relocate_sys_chunks()
Josef Bacik (1):
btrfs: take the cleaner_mutex earlier in qgroup disable
Qu Wenruo (1):
btrfs: set correct ram_bytes when splitting ordered extent
fs/btrfs/ioctl.c | 33 ++++++++++++++++++++++++++++++---
fs/btrfs/ordered-data.c | 1 +
fs/btrfs/qgroup.c | 21 ++++++++-------------
fs/btrfs/volumes.c | 1 +
4 files changed, 40 insertions(+), 16 deletions(-)
next reply other threads:[~2024-05-02 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 12:57 David Sterba [this message]
2024-05-02 17:57 ` [GIT PULL] Btrfs fixes for 6.9-rc7 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.1714654371.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