All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: [PATCH 0/3] Send: minor cleanups, add RO checks
Date: Mon, 16 Dec 2013 17:34:07 +0100	[thread overview]
Message-ID: <cover.1387211245.git.dsterba@suse.cz> (raw)

First two patches are trivial cleanups that I've spotted while reading send.c,
can be applied independently.

The third patch contains the important bits, safety checks that the subvolumes
involved in send do not accidentally lose the RO status. I haven't seen this
documented anywhere that this is mandatory, implied from how I assume send
works. Please let me know if this is wrong.

David Sterba (3):
  btrfs: send: clean up dead code
  btrfs: remove unused mnt from send_ctx
  btrfs: Check read-only status of roots during send

 fs/btrfs/ctree.h |    6 +++
 fs/btrfs/ioctl.c |   22 +++++++++-
 fs/btrfs/send.c  |  116 +++++++++++++++++++++++++++++-------------------------
 3 files changed, 87 insertions(+), 57 deletions(-)

-- 
1.7.9


             reply	other threads:[~2013-12-16 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 16:34 David Sterba [this message]
2013-12-16 16:34 ` [PATCH 1/3] btrfs: send: clean up dead code David Sterba
2013-12-16 16:34 ` [PATCH 2/3] btrfs: remove unused mnt from send_ctx David Sterba
2013-12-16 16:34 ` [PATCH 3/3] btrfs: Check read-only status of roots during send David Sterba
2013-12-17 11:58   ` Wang Shilong
2013-12-17 13:09     ` David Sterba
2013-12-17 14:07 ` 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.1387211245.git.dsterba@suse.cz \
    --to=dsterba@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.