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.12-rc7
Date: Fri, 8 Nov 2024 14:45:10 +0100 [thread overview]
Message-ID: <cover.1731071660.git.dsterba@suse.com> (raw)
Hi,
a few more one-liners that fix some user visible problems. Please pull,
thanks.
- use correct range when clearing qgroup reservations after COW
- properly reset freed delayed ref list head
- fix ro/rw subvolume mounts to be backward compatible with old and new
mount API
----------------------------------------------------------------
The following changes since commit 77b0d113eec49a7390ff1a08ca1923e89f5f86c6:
btrfs: fix defrag not merging contiguous extents due to merged extent maps (2024-10-31 16:46:41 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.12-rc6-tag
for you to fetch changes up to 2b084d8205949dd804e279df8e68531da78be1e8:
btrfs: fix the length of reserved qgroup to free (2024-11-07 02:08:29 +0100)
----------------------------------------------------------------
Filipe Manana (1):
btrfs: reinitialize delayed ref list after deleting it from the list
Haisu Wang (1):
btrfs: fix the length of reserved qgroup to free
Qu Wenruo (1):
btrfs: fix per-subvolume RO/RW flags with new mount API
fs/btrfs/delayed-ref.c | 2 +-
fs/btrfs/inode.c | 2 +-
fs/btrfs/super.c | 25 +++++--------------------
3 files changed, 7 insertions(+), 22 deletions(-)
next reply other threads:[~2024-11-08 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 13:45 David Sterba [this message]
2024-11-08 17:39 ` [GIT PULL] Btrfs fixes for 6.12-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.1731071660.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