From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: small changes to "usebackuproot" mount
Date: Fri, 3 Jul 2026 09:10:12 +0930 [thread overview]
Message-ID: <cover.1783035512.git.wqu@suse.com> (raw)
"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.
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 second patch.
Qu Wenruo (2):
btrfs: add "rescue=usebackuproot" into forced read-only options
btrfs: remove "usebackuproot" mount option
fs/btrfs/super.c | 14 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
--
2.54.0
next reply other threads:[~2026-07-02 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 23:40 Qu Wenruo [this message]
2026-07-02 23:40 ` [PATCH 1/2] btrfs: add "rescue=usebackuproot" into forced read-only options Qu Wenruo
2026-07-03 2:33 ` Dongjiang Zhu
2026-07-03 3:19 ` Qu Wenruo
2026-07-02 23:40 ` [PATCH 2/2] btrfs: remove "usebackuproot" mount option 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.1783035512.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