From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/5] btrfs-progs: almost full support for RAID56J profiles
Date: Sun, 15 May 2022 18:54:55 +0800 [thread overview]
Message-ID: <cover.1652611957.git.wqu@suse.com> (raw)
This is the progs companion for the new RAID56J profiles.
Unlike kernel part, progs doesn't really need to implement the full
journal, thus the following basic features should be enough:
- Mkfs support
- Check support (both original and lowmem mode)
- Print tree support
The final patch is a fix for a leakage of path which is exposed during
kernel development.
Qu Wenruo (5):
btrfs-progs: introduce the basic support for RAID56J feature
btrfs-progs: mkfs: add support for RAID56J creation
btrfs-progs: check: take per device reservation into consideration
btrfs-progs: print-tree: add support for per_dev_reserved of chunk
item
btrfs-progs: check/lowmem: fix path leakage when dev extents are
invalid
check/common.h | 7 ++-
check/main.c | 16 ++++--
check/mode-lowmem.c | 17 ++++--
cmds/filesystem-usage.c | 6 ++-
cmds/rescue-chunk-recover.c | 13 +++--
common/fsfeatures.c | 9 ++++
common/utils.c | 6 ++-
kernel-shared/ctree.h | 42 +++++++++++++--
kernel-shared/extent-tree.c | 18 +++++--
kernel-shared/print-tree.c | 5 +-
kernel-shared/volumes.c | 105 +++++++++++++++++++++++++++++++-----
kernel-shared/volumes.h | 2 +
mkfs/main.c | 3 ++
13 files changed, 205 insertions(+), 44 deletions(-)
--
2.36.1
next reply other threads:[~2022-05-15 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 10:54 Qu Wenruo [this message]
2022-05-15 10:54 ` [PATCH 1/5] btrfs-progs: introduce the basic support for RAID56J feature Qu Wenruo
2022-05-15 10:54 ` [PATCH 2/5] btrfs-progs: mkfs: add support for RAID56J creation Qu Wenruo
2022-05-15 10:54 ` [PATCH 3/5] btrfs-progs: check: take per device reservation into consideration Qu Wenruo
2022-05-15 10:54 ` [PATCH 4/5] btrfs-progs: print-tree: add support for per_dev_reserved of chunk item Qu Wenruo
2022-05-15 10:55 ` [PATCH 5/5] btrfs-progs: check/lowmem: fix path leakage when dev extents are invalid Qu Wenruo
2022-05-15 18:15 ` Nikolay Borisov
2022-05-17 19:03 ` 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.1652611957.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