From: Miao Xie <miaox@cn.fujitsu.com>
To: Liu Bo <bo.li.liu@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/3] Btrfs: fix EEXIST error when creating new file in subvolume/snapshot
Date: Fri, 13 Dec 2013 17:46:55 +0800 [thread overview]
Message-ID: <52AAD78F.206@cn.fujitsu.com> (raw)
In-Reply-To: <1386926183-18325-4-git-send-email-bo.li.liu@oracle.com>
On fri, 13 Dec 2013 17:16:23 +0800, Liu Bo wrote:
> While creating a subvolume/snapshot, we don't use inode cache to allocate
> an inode id for the root dir "..", so inode cache doesn't mark that id as
FIRST_FREE_OBJECTID should be the root dir ".", not "..".
The other is OK for me.
Reviewed-by: Miao Xie <miaox@cn.fujitsu.com>
> used, and when we create a new file, it'll find that fact and throw out
> -EEXIST.
>
> Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> ---
> fs/btrfs/inode-map.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/inode-map.c b/fs/btrfs/inode-map.c
> index 493694f..bcff910 100644
> --- a/fs/btrfs/inode-map.c
> +++ b/fs/btrfs/inode-map.c
> @@ -528,6 +528,16 @@ static int btrfs_find_highest_objectid(struct btrfs_root *root, u64 *objectid)
> struct btrfs_key search_key;
> struct btrfs_key found_key;
> int slot;
> + u64 min_objectid;
> +
> + /*
> + * For fs/file tree, FIRST_FREE_OBJECTID is reserved for
> + * root dir ".."
> + */
> + if (is_fstree(root->root_key.objectid))
> + min_objectid = BTRFS_FIRST_FREE_OBJECTID;
> + else
> + min_objectid = BTRFS_FIRST_FREE_OBJECTID - 1;
>
> path = btrfs_alloc_path();
> if (!path)
> @@ -544,10 +554,9 @@ static int btrfs_find_highest_objectid(struct btrfs_root *root, u64 *objectid)
> slot = path->slots[0] - 1;
> l = path->nodes[0];
> btrfs_item_key_to_cpu(l, &found_key, slot);
> - *objectid = max_t(u64, found_key.objectid,
> - BTRFS_FIRST_FREE_OBJECTID - 1);
> + *objectid = max_t(u64, found_key.objectid, min_objectid);
> } else {
> - *objectid = BTRFS_FIRST_FREE_OBJECTID - 1;
> + *objectid = min_objectid;
> }
> ret = 0;
> error:
>
prev parent reply other threads:[~2013-12-13 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 9:16 [PATCH 0/3] Btrfs: inode cache fixes Liu Bo
2013-12-13 9:16 ` [PATCH 1/3] Btrfs: avoid building inode cache repeatly Liu Bo
2013-12-13 9:38 ` Miao Xie
2013-12-13 9:16 ` [PATCH 2/3] Btrfs: don't build inode cache for orphan root Liu Bo
2013-12-13 9:43 ` Miao Xie
2013-12-13 9:16 ` [PATCH 3/3] Btrfs: fix EEXIST error when creating new file in subvolume/snapshot Liu Bo
2013-12-13 9:46 ` Miao Xie [this message]
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=52AAD78F.206@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=bo.li.liu@oracle.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;
as well as URLs for NNTP newsgroup(s).