All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: dsterba@suse.com, linux-btrfs@vger.kernel.org,
	Marcos Paulo de Souza <mpdesouza@suse.com>,
	wqu@suse.com
Subject: [PATCH 0/2] fs: btrfs: Introduce deleting subvolume by subvolid
Date: Sat, 11 Jan 2020 01:39:40 -0300	[thread overview]
Message-ID: <20200111043942.15366-1-marcos.souza.org@gmail.com> (raw)

From: Marcos Paulo de Souza <mpdesouza@suse.com>

The first patch separates the subvolume lookup and deletion into a new function,
and second only get the dentry related to the subvolume id and calls this
function.

Please let me know if these patches need improvement. Thanks!

Marcos Paulo de Souza (2):
  btrfs: ioctl: Move the subvolume deleter code into a new function
  btrfs: Introduce new BTRFS_IOC_SNAP_DESTROY_V2 ioctl

 fs/btrfs/ctree.h           |   8 +++
 fs/btrfs/export.c          |   4 +-
 fs/btrfs/ioctl.c           | 119 ++++++++++++++++++++++++++++---------
 fs/btrfs/super.c           |   2 +-
 include/uapi/linux/btrfs.h |  12 +++-
 5 files changed, 113 insertions(+), 32 deletions(-)

-- 
2.24.0


             reply	other threads:[~2020-01-11  4:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-11  4:39 Marcos Paulo de Souza [this message]
2020-01-11  4:39 ` [PATCH 1/2] btrfs: ioctl: Move the subvolume deleter code into a new function Marcos Paulo de Souza
2020-01-11  4:39 ` [PATCH 2/2] btrfs: Introduce new BTRFS_IOC_SNAP_DESTROY_V2 ioctl Marcos Paulo de Souza
2020-01-13 17:37   ` Josef Bacik
2020-01-14  2:31     ` Marcos Paulo de Souza
2020-01-14  2:40       ` Josef Bacik

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=20200111043942.15366-1-marcos.souza.org@gmail.com \
    --to=marcos.souza.org@gmail.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpdesouza@suse.com \
    --cc=wqu@suse.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 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.