From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH FOR v7.1 0/2] btrfs: move some features out of experimental
Date: Tue, 10 Feb 2026 14:32:56 +1030 [thread overview]
Message-ID: <cover.1770695952.git.wqu@suse.com> (raw)
The two features can be moved out of experimental in v7.1:
- Large data folios
It's introduced in v6.17, but we still have a bug fix related for it
in v6.19.
If there is no new bug exposed I believe it's time to expose this
feature to end users.
- Shutdown and remove_bdev callbacks
It's introduced in v6.19, but there is no major known bug exposed yet.
Furthermore the remove_bdev callback, aka auto-shutdown/degradation
when a device is missing, can affect end users.
Thus we want some feedbacks from early adopters.
Qu Wenruo (2):
btrfs: move shutdown and remove_bdev callbacks out of experimental
features
btrfs: move larger data folios out of experimental features
fs/btrfs/Kconfig | 4 +---
fs/btrfs/btrfs_inode.h | 2 --
fs/btrfs/super.c | 4 ----
3 files changed, 1 insertion(+), 9 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-10 4:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 4:02 Qu Wenruo [this message]
2026-02-10 4:02 ` [PATCH 1/2] btrfs: move shutdown and remove_bdev callbacks out of experimental features Qu Wenruo
2026-02-10 4:02 ` [PATCH 2/2] btrfs: move larger data folios " Qu Wenruo
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.1770695952.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.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