From: David Sterba <dsterba@suse.cz>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/5] Btrfs: maintain subvolume items in the UUID tree
Date: Mon, 29 Apr 2013 16:50:13 +0200 [thread overview]
Message-ID: <20130429145013.GR16427@twin.jikos.cz> (raw)
In-Reply-To: <a1d5f4c0cad1e70800a8b678df684f03c8251cf9.1366384796.git.sbehrens@giantdisaster.de>
On Fri, Apr 19, 2013 at 05:41:05PM +0200, Stefan Behrens wrote:
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -57,6 +57,8 @@
> #include "send.h"
> #include "dev-replace.h"
>
> +static char empty_uuid[BTRFS_UUID_SIZE] = {0};
+ const
> @@ -567,9 +573,10 @@ static int create_snapshot(struct btrfs_root *root, struct inode *dir,
> * 1 - root item
> * 2 - root ref/backref
> * 1 - root of snapshot
> + * 1 - UUID item
> */
> ret = btrfs_subvolume_reserve_metadata(BTRFS_I(dir)->root,
> - &pending_snapshot->block_rsv, 7,
> + &pending_snapshot->block_rsv, 8,
> &pending_snapshot->qgroup_reserved);
> if (ret)
> goto out;
> @@ -580,7 +587,7 @@ static int create_snapshot(struct btrfs_root *root, struct inode *dir,
> pending_snapshot->dir = dir;
> pending_snapshot->inherit = inherit;
>
> - trans = btrfs_start_transaction(root, 0);
> + trans = btrfs_start_transaction(root->fs_info->extent_root, 8);
This look suspicious in 2 ways:
* why is root switched to extent_root
* what's the reason of 8 units being reserved
> if (IS_ERR(trans)) {
> ret = PTR_ERR(trans);
> goto fail;
> @@ -3925,7 +3954,7 @@ static long btrfs_ioctl_set_received_subvol(struct file *file,
> goto out;
> }
>
> - trans = btrfs_start_transaction(root, 1);
> + trans = btrfs_start_transaction(root, 3);
Please document what's being reserved
> if (IS_ERR(trans)) {
> ret = PTR_ERR(trans);
> trans = NULL;
> --- a/fs/btrfs/transaction.c
> +++ b/fs/btrfs/transaction.c
> @@ -34,6 +34,8 @@
>
> #define BTRFS_ROOT_TRANS_TAG 0
>
> +static char empty_uuid[BTRFS_UUID_SIZE] = {0};
second empty_uuid? well, alternatively you could implement a helper
"is uuid empty" and compare to zeros directly
> +
> void put_transaction(struct btrfs_transaction *transaction)
> {
> WARN_ON(atomic_read(&transaction->use_count) == 0);
next prev parent reply other threads:[~2013-04-29 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 15:41 [PATCH 0/5] Btrfs: introduce a tree for UUID to subvol ID mapping Stefan Behrens
2013-04-19 15:41 ` [PATCH 1/5] Btrfs: introduce a tree for items that map UUIDs to something Stefan Behrens
2013-04-29 19:27 ` Josef Bacik
2013-04-19 15:41 ` [PATCH 2/5] Btrfs: support printing UUID tree elements Stefan Behrens
2013-04-29 14:31 ` David Sterba
2013-04-19 15:41 ` [PATCH 3/5] Btrfs: create UUID tree if required Stefan Behrens
2013-04-29 14:35 ` David Sterba
2013-04-19 15:41 ` [PATCH 4/5] Btrfs: maintain subvolume items in the UUID tree Stefan Behrens
2013-04-29 14:50 ` David Sterba [this message]
2013-04-19 15:41 ` [PATCH 5/5] Btrfs: fill UUID tree initially Stefan Behrens
2013-04-29 15:12 ` David Sterba
2013-04-29 17:31 ` Stefan Behrens
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=20130429145013.GR16427@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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