From: Mark Fasheh <mfasheh@suse.de>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@fusionio.com>
Subject: Re: [PATCH 1/3] btrfs: extended inode refs
Date: Tue, 14 Aug 2012 09:51:40 -0700 [thread overview]
Message-ID: <20120814165140.GC15159@wotan.suse.de> (raw)
In-Reply-To: <502A1B3B.3050804@jan-o-sch.net>
On Tue, Aug 14, 2012 at 11:32:43AM +0200, Jan Schmidt wrote:
> On Wed, August 08, 2012 at 20:55 (+0200), Mark Fasheh wrote:
> > +/*
> > + * btrfs_insert_inode_extref() - Inserts an extended inode ref into a tree.
> > + *
> > + * The caller must have checked against BTRFS_LINK_MAX already.
> > + */
> > +static int btrfs_insert_inode_extref(struct btrfs_trans_handle *trans,
> > + struct btrfs_root *root,
> > + const char *name, int name_len,
> > + u64 inode_objectid, u64 ref_objectid, u64 index)
> > +{
> > + struct btrfs_inode_extref *extref;
> > + int ret;
> > + int ins_len = name_len + sizeof(*extref);
> > + unsigned long ptr;
> > + struct btrfs_path *path;
> > + struct btrfs_key key;
> > + struct extent_buffer *leaf;
> > + struct btrfs_item *item;
> > +
> > + key.objectid = inode_objectid;
> > + key.type = BTRFS_INODE_EXTREF_KEY;
> > + key.offset = btrfs_extref_hash(ref_objectid, name, name_len);
> > +
> > + path = btrfs_alloc_path();
> > + if (!path)
> > + return -ENOMEM;
> > +
> > + path->leave_spinning = 1;
> > + ret = btrfs_insert_empty_item(trans, root, path, &key,
> > + ins_len);
> > + if (ret == -EEXIST) {
> > + if (btrfs_find_name_in_ext_backref(path, name, name_len, NULL))
> > + goto out;
> > +
> > + btrfs_extend_item(trans, root, path, ins_len);
> > + }
> > + if (ret < 0)
> > + goto out;
>
> This doesn't look right. Did you actually test it? I haven't, but I claim that
> with this version of the patch, you won't be able to add a hash collision link.
>
> Jeff changed btrfs_extend_item from int to void in March, so we're no longer
> setting ret there. I suggest adding "ret = 0" within the EEXIST-block.
Doh, yeah I didn't test collisions on this version of the patch (as you can
obviously see, I messed up the merge of Jeff's change).
> The rest of this patch looks good to me.
Awesome, I'll send the above as a fix to this patch series (I have at least
one other fix to send soon too)
--Mark
--
Mark Fasheh
next prev parent reply other threads:[~2012-08-14 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 18:55 [PATCH 0/3] btrfs: extended inode refs Mark Fasheh
2012-08-08 18:55 ` [PATCH 1/3] " Mark Fasheh
2012-08-14 9:32 ` Jan Schmidt
2012-08-14 16:51 ` Mark Fasheh [this message]
2012-08-08 18:55 ` [PATCH 2/3] " Mark Fasheh
2012-08-15 15:04 ` Jan Schmidt
2012-08-15 17:59 ` Mark Fasheh
2012-08-08 18:55 ` [PATCH 3/3] " Mark Fasheh
2012-08-15 8:46 ` Jan Schmidt
-- strict thread matches above, loose matches on Subject: below --
2012-05-21 21:46 [PATCH 0/3] " Mark Fasheh
2012-05-21 21:46 ` [PATCH 1/3] " Mark Fasheh
2012-07-06 14:56 ` Jan Schmidt
2012-07-06 15:14 ` Stefan Behrens
2012-07-09 19:05 ` Mark Fasheh
2012-07-09 20:33 ` Mark Fasheh
2012-04-05 20:09 [PATCH 0/3] " Mark Fasheh
2012-04-05 20:09 ` [PATCH 1/3] " Mark Fasheh
2012-04-12 13:08 ` Jan Schmidt
2012-04-24 22:23 ` Mark Fasheh
2012-04-25 10:19 ` Jan Schmidt
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=20120814165140.GC15159@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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).