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-rc5
Date: Wed, 23 Oct 2024 18:07:39 +0200 [thread overview]
Message-ID: <cover.1729698780.git.dsterba@suse.com> (raw)
Hi,
please pull the following fixes, all for stable trees. Thanks.
- mount option fixes:
- fix handling of compression mount options on remount
- reject rw remount in case there are options that don't work in
read-write mode (like rescue options)
- fix zone accounting of unusable space
- fix in-memory corruption when merging extent maps
- fix delalloc range locking for sector < page
- use more convenient default value of drop subtree threshold, clean
more subvolumes without the fallback to marking quotas inconsistent
- fix smatch warning about incorrect value passed to ERR_PTR
----------------------------------------------------------------
The following changes since commit 2ab5e243c2266c841e0f6904fad1514b18eaf510:
btrfs: fix uninitialized pointer free on read_alloc_one_name() error (2024-10-11 19:55:04 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.12-rc4-tag
for you to fetch changes up to 75f49c3dc7b7423d3734f2e4dabe3dac8d064338:
btrfs: fix passing 0 to ERR_PTR in btrfs_search_dir_index_item() (2024-10-22 16:10:55 +0200)
----------------------------------------------------------------
Boris Burkov (1):
btrfs: fix read corruption due to race with extent map merging
Filipe Manana (1):
btrfs: clear force-compress on remount when compress mount option is given
Naohiro Aota (1):
btrfs: zoned: fix zone unusable accounting for freed reserved extent
Qu Wenruo (3):
btrfs: qgroup: set a more sane default value for subtree drop threshold
btrfs: fix the delalloc range locking if sector size < page size
btrfs: reject ro->rw reconfiguration if there are hard ro requirements
Yue Haibing (1):
btrfs: fix passing 0 to ERR_PTR in btrfs_search_dir_index_item()
fs/btrfs/block-group.c | 2 ++
fs/btrfs/dir-item.c | 4 ++--
fs/btrfs/disk-io.c | 2 +-
fs/btrfs/extent_io.c | 17 +++++++++--------
fs/btrfs/extent_map.c | 31 ++++++++++++++++---------------
fs/btrfs/inode.c | 7 ++-----
fs/btrfs/qgroup.c | 2 +-
fs/btrfs/qgroup.h | 2 ++
fs/btrfs/super.c | 12 ++++++++++--
9 files changed, 45 insertions(+), 34 deletions(-)
next reply other threads:[~2024-10-23 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 16:07 David Sterba [this message]
2024-10-24 20:33 ` [GIT PULL] Btrfs fixes for 6.12-rc5 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.1729698780.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