From: Andreas Philipp <philipp.andreas@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Andreas Philipp <philipp.andreas@gmail.com>,
chris.mason@oracle.com, dcrmorgado@gmail.com, kreijack@libero.it,
lizf@cn.fujitsu.com
Subject: [PATCH v2 0/5] Add user-space support for read-only snapshot creation.
Date: Tue, 26 Apr 2011 10:02:39 +0200 [thread overview]
Message-ID: <1303804964-2840-1-git-send-email-philipp.andreas@gmail.com> (raw)
In-Reply-To: <There is kernel side support for the creation of read-only snapshots>
Changelog v2:
- Fixed uninitialized variable (args).
- Corrected order of patches to make everything compile.
- Fixed some style errors.
There is kernel side support for the creation of read-only snapshots
for some time now, but I did not find any patches for the userspace
btrfs utilites. Thus I created this patchset which is tested and
working with kernel version 2.6.39-rc2.
Andreas Philipp (5):
Added support for an additional ioctl.
Add support for read-only subvolumes.
Support the new parameters in do_clone(int argc, char** argv).
Test the additional ioctl.
Updated manpage for btrfs subvolume snapshot.
btrfs.c | 6 +++---
btrfs_cmds.c | 48 ++++++++++++++++++++++++++++++++++++++++--------
ioctl-test.c | 1 +
ioctl.h | 14 ++++++++++++++
man/btrfs.8.in | 11 ++++++-----
5 files changed, 64 insertions(+), 16 deletions(-)
--
1.7.4.1
next parent reply other threads:[~2011-04-26 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <There is kernel side support for the creation of read-only snapshots>
2011-04-26 8:02 ` Andreas Philipp [this message]
2011-04-26 8:02 ` [PATCH 1/5] Added support for an additional ioctl Andreas Philipp
2011-04-26 8:02 ` [PATCH 2/5] Add support for read-only subvolumes Andreas Philipp
2011-04-26 8:02 ` [PATCH 3/5] Support the new parameters in do_clone(int argc, char** argv) Andreas Philipp
2011-04-26 8:02 ` [PATCH 4/5] Test the additional ioctl Andreas Philipp
2011-04-26 8:02 ` [PATCH 5/5] Updated manpage for btrfs subvolume snapshot Andreas Philipp
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=1303804964-2840-1-git-send-email-philipp.andreas@gmail.com \
--to=philipp.andreas@gmail.com \
--cc=chris.mason@oracle.com \
--cc=dcrmorgado@gmail.com \
--cc=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
/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;
as well as URLs for NNTP newsgroup(s).