From: Christoph Hellwig <hch@infradead.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Balaji Rao <balajirrao@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/3] Introduce btrfs_iget helper
Date: Tue, 12 Aug 2008 14:46:54 -0400 [thread overview]
Message-ID: <20080812184654.GA29426@infradead.org> (raw)
In-Reply-To: <1218548800.2977.178.camel@pmac.infradead.org>
> +struct inode *btrfs_iget(struct super_block *s, struct btrfs_key *location,
> + struct btrfs_root *root, int *is_new)
> +{
> + struct inode *inode;
> +
> + inode = btrfs_iget_locked(s, location->objectid, root);
> + if (!inode)
> + return ERR_PTR(-EACCES);
> +
> + if (inode->i_state & I_NEW) {
> + BTRFS_I(inode)->root = root;
> + memcpy(&BTRFS_I(inode)->location, location, sizeof(*location));
> + btrfs_read_locked_inode(inode);
> + unlock_new_inode(inode);
> + if (is_new)
> + *is_new = 1;
> + } else {
> + if (is_new)
> + *is_new = 0;
> + }
> +
> + return inode;
Please leave the unlock_new_inode to the caller and kill the is_new
parameter. Gives much nicer to read code, and generally making sure the
inode is 100% ready and correct before unlocking it is a good idea, too
so that e.g. no one can actually access an inode marked bad due to a
generation number mismatch before it's marked bad.
> +}
> +
> static struct dentry *btrfs_lookup(struct inode *dir, struct dentry *dentry,
> struct nameidata *nd)
> {
> @@ -1889,7 +1916,7 @@ static struct dentry *btrfs_lookup(struct inode *dir, struct dentry *dentry,
> struct btrfs_root *root = bi->root;
> struct btrfs_root *sub_root = root;
> struct btrfs_key location;
> - int ret, do_orphan = 0;
> + int ret, new, do_orphan = 0;
>
> if (dentry->d_name.len > BTRFS_NAME_LEN)
> return ERR_PTR(-ENAMETOOLONG);
> @@ -1907,23 +1934,15 @@ static struct dentry *btrfs_lookup(struct inode *dir, struct dentry *dentry,
> return ERR_PTR(ret);
> if (ret > 0)
> return ERR_PTR(-ENOENT);
> -
> - inode = btrfs_iget_locked(dir->i_sb, location.objectid,
> - sub_root);
> - if (!inode)
> - return ERR_PTR(-EACCES);
> - if (inode->i_state & I_NEW) {
> - /* the inode and parent dir are two different roots */
> - if (sub_root != root) {
> - igrab(inode);
> - sub_root->inode = inode;
> - do_orphan = 1;
> - }
> - BTRFS_I(inode)->root = sub_root;
> - memcpy(&BTRFS_I(inode)->location, &location,
> - sizeof(location));
> - btrfs_read_locked_inode(inode);
> - unlock_new_inode(inode);
> + inode = btrfs_iget(dir->i_sb, &location, sub_root, &new);
> + if (IS_ERR(inode))
> + return ERR_CAST(inode);
> +
> + /* the inode and parent dir are two different roots */
> + if (new && root != sub_root) {
> + igrab(inode);
> + sub_root->inode = inode;
> + do_orphan = 1;
> }
> }
>
> --
> 1.5.5.1
>
>
> --
> David Woodhouse Open Source Technology Centre
> David.Woodhouse@intel.com Intel Corporation
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
---end quoted text---
next prev parent reply other threads:[~2008-08-12 18:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 23:35 [RFC] NFS Support Balaji Rao
2008-06-30 14:50 ` Josef Bacik
2008-06-30 15:20 ` Balaji Rao R
2008-06-30 15:08 ` Josef Bacik
2008-07-01 7:01 ` Christoph Hellwig
2008-06-30 18:46 ` Christoph Hellwig
2008-08-12 13:46 ` [PATCH 1/3] Introduce btrfs_iget helper David Woodhouse
2008-08-12 18:46 ` Christoph Hellwig [this message]
2008-08-13 9:07 ` David Woodhouse
2008-08-13 9:41 ` David Woodhouse
2008-08-12 13:46 ` [PATCH 2/3] NFS support for btrfs - v2 David Woodhouse
2008-08-12 18:51 ` Christoph Hellwig
2008-08-13 8:53 ` David Woodhouse
2008-08-13 15:06 ` [PATCH 2/3] NFS support for btrfs - v3 David Woodhouse
2008-08-12 13:46 ` [PATCH 3/3] Implement our own copy of the nfsd readdir hack, for older kernels David Woodhouse
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=20080812184654.GA29426@infradead.org \
--to=hch@infradead.org \
--cc=balajirrao@gmail.com \
--cc=dwmw2@infradead.org \
--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