From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/3] btrfs: small changes to "usebackuproot" mount option
Date: Fri, 3 Jul 2026 19:16:05 +0930 [thread overview]
Message-ID: <cover.1783071857.git.wqu@suse.com> (raw)
[CHANGELOG]
v3:
- Add "rescue=usebackuproot" into full RO mount options
- Minor grammar updates
v2:
- Also include "rescue=usebackuproot" into "rescue=all" shortcut
"rescue=usebackuproot" mount option is not requiring a read-only mount,
which is different from all the other options in the "rescue=" group.
Address that in the first patch.
Then also include "rescue=usebackuproot" into "rescue=all" group, done
in the second patch.
Standalone "usebackuproot" mount option is already marked deprecated
since v5.9, I see no practical reason to keep supporting it in 2026.
Just remove it in the last patch.
Qu Wenruo (3):
btrfs: add "rescue=usebackuproot" into forced read-only options
btrfs: add "rescue=usebackuproot" into "rescue=all" shortcut
btrfs: remove "usebackuproot" mount option
fs/btrfs/fs.h | 3 ++-
fs/btrfs/super.c | 16 +++-------------
2 files changed, 5 insertions(+), 14 deletions(-)
--
2.54.0
next reply other threads:[~2026-07-03 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 9:46 Qu Wenruo [this message]
2026-07-03 9:46 ` [PATCH v3 1/3] btrfs: add "rescue=usebackuproot" into forced read-only options Qu Wenruo
2026-07-03 9:46 ` [PATCH v3 2/3] btrfs: add "rescue=usebackuproot" into "rescue=all" shortcut Qu Wenruo
2026-07-03 9:46 ` [PATCH v3 3/3] btrfs: remove "usebackuproot" mount option Qu Wenruo
2026-07-03 10:27 ` Johannes Thumshirn
2026-07-03 10:27 ` [PATCH v3 0/3] btrfs: small changes to " Johannes Thumshirn
2026-07-03 17:06 ` Neal Gompa
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.1783071857.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 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.