From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/5] Subvolume ro/rw and received_uuid
Date: Fri, 1 Oct 2021 17:28:54 +0200 [thread overview]
Message-ID: <cover.1633101904.git.dsterba@suse.com> (raw)
Here's implemented the userspace prevention of accidental ro->rw switch
of sent subvolumes. It's not finialized but the main idea is there so
here we go argue, as we haven't reached a consensus with Nikolay what is
the right usability approach.
There are two patches extending the printed information about root items
and subvolumes but they're only for convenience, that I also used for
debugging.
David Sterba (5):
btrfs-progs: subvol show: print send and receive generation and
timestamp
btrfs-progs: dump-tree: print complete root_item
btrfs-progs: props: add force parameter to set
btrfs-progs: property: ro->rw and received_uuid
btrfs-progs: tests: subvolume ro->rw switch and received_uuid
cmds/property.c | 99 ++++++++++++++++---
cmds/props.h | 3 +-
cmds/subvolume.c | 21 ++++
kernel-shared/print-tree.c | 53 +++++-----
.../050-receive-prop-ro-to-rw/test.sh | 42 ++++++++
5 files changed, 172 insertions(+), 46 deletions(-)
create mode 100755 tests/misc-tests/050-receive-prop-ro-to-rw/test.sh
--
2.33.0
next reply other threads:[~2021-10-01 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 15:28 David Sterba [this message]
2021-10-01 15:28 ` [PATCH 1/5] btrfs-progs: subvol show: print send and receive generation and timestamp David Sterba
2021-10-01 15:28 ` [PATCH 2/5] btrfs-progs: dump-tree: print complete root_item David Sterba
2021-10-01 15:29 ` [PATCH 3/5] btrfs-progs: props: add force parameter to set David Sterba
2021-10-01 15:29 ` [PATCH 4/5] btrfs-progs: property: ro->rw and received_uuid David Sterba
2021-10-02 7:05 ` Andrei Borzenkov
2021-10-04 15:22 ` David Sterba
2021-10-04 10:10 ` Nikolay Borisov
2021-10-04 15:21 ` David Sterba
2021-10-01 15:29 ` [PATCH 5/5] btrfs-progs: tests: subvolume ro->rw switch " David Sterba
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.1633101904.git.dsterba@suse.com \
--to=dsterba@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