From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs-progs: subvolume create: accept multiple arguments
Date: Thu, 2 Nov 2023 16:03:47 +1030 [thread overview]
Message-ID: <cover.1698903010.git.wqu@suse.com> (raw)
This patchset adds the ability to accept multiple arguments for "btrfs
subvolume create" command, just like "mkdir".
And also we follow the error reporting part of "mkdir", any failure
would make the command to return 1 for error.
[PATCHSET STRUCTURE]
During the development, I found two missing error handling for strdup(),
thus here comes the first patch to fix them.
Then the 2nd patch implements the main part.
Finally the last patch is add the new test case for the error handling
part.
Qu Wenruo (3):
btrfs-progs: subvolume create: handle failure for strdup()
btrfs-progs: subvolume create: accept multiple arguments
btrfs-progs: cli-tests: add test case for subvolume create multiple
arguments
Documentation/btrfs-subvolume.rst | 11 +-
cmds/subvolume.c | 223 ++++++++++--------
.../021-subvolume-multiple-arguments/test.sh | 37 +++
3 files changed, 170 insertions(+), 101 deletions(-)
create mode 100755 tests/cli-tests/021-subvolume-multiple-arguments/test.sh
--
2.42.0
next reply other threads:[~2023-11-02 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 5:33 Qu Wenruo [this message]
2023-11-02 5:33 ` [PATCH 1/3] btrfs-progs: subvolume create: handle failure for strdup() Qu Wenruo
2023-11-23 19:11 ` David Sterba
2023-11-02 5:33 ` [PATCH 2/3] btrfs-progs: subvolume create: accept multiple arguments Qu Wenruo
2023-11-02 5:33 ` [PATCH 3/3] btrfs-progs: cli-tests: add test case for subvolume create " Qu Wenruo
2023-11-23 19:22 ` [PATCH 0/3] btrfs-progs: subvolume create: accept " 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.1698903010.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