From: Josef Bacik <jbacik@redhat.com>
To: Balaji Rao R <balajirrao@gmail.com>
Cc: Josef Bacik <jbacik@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: [RFC] NFS Support
Date: Mon, 30 Jun 2008 11:08:11 -0400 [thread overview]
Message-ID: <20080630150811.GB18866@unused.rdu.redhat.com> (raw)
In-Reply-To: <569c97d20806300820p1e6f3b9eha359f93ea41c6705@mail.gmail.com>
On Mon, Jun 30, 2008 at 08:50:46PM +0530, Balaji Rao R wrote:
> On Mon, Jun 30, 2008 at 8:20 PM, Josef Bacik <jbacik@redhat.com> wrote:
> > On Sun, Jun 29, 2008 at 05:05:31AM +0530, Balaji Rao wrote:
> >> Hello,
> >>
> >> Here's a quick implementation of NFS support for btrfs. It works mostly. But
> >> its still a bit buggy. I suspect it has to do something with inode locking.
> >> When I unmount and mount a couple of times, it stops working i.e, when I do an
> >> 'ls', it keeps waiting indefinitely. This is seen when accessing the filesystem
> >> from a local mount point as well.
> >>
> >> Can anybody please review and tell me what stupid mistake I'm committing ?
> >>
> >
> > You may want to send things in patch form. I'd recommend using the hg quilt
> > plugin, its nice for adding patches easily.
> Yes, since this was just an RFC, i thought it would be better to send
> just the file I created.
> >
> >>
> >> #include <linux/fs.h>
> >> #include <linux/types.h>
> >> #include "ctree.h"
> >> #include "disk-io.h"
> >> #include "btrfs_inode.h"
> >> #include "print-tree.h"
> >> #include "export.h"
> >>
> >> static int btrfs_encode_fh(struct dentry *dentry, u32 *fh_in, int *max_len,
> >> int connectable)
> >> { struct inode *inode = dentry->d_inode;
> >> int len = *max_len;
> >> u64 objectid, root_objectid;
> >> u32 generation;
> >> __le32 *fh = (__force __le32 *) fh_in;
> >>
> >> if ((len < 5 )|| (connectable && len < 8)) {
> >> return 255;
> >> }
> >
> > Magic numbers are a no-no.
> OK :) Will change
> >
> >>
> >> objectid = BTRFS_I(inode)->location.objectid;
> >> root_objectid = BTRFS_I(inode)->root->objectid;
> >> generation = inode->i_generation;
> >>
> >> len = 5;
> >> fh[0] = cpu_to_le32((u32)(objectid >> 32));
> >> fh[1] = cpu_to_le32((u32)(objectid & 0xffffffff));
> >> fh[2] = cpu_to_le32((u32)(root_objectid >> 32));
> >> fh[3] = cpu_to_le32((u32)(root_objectid & 0xffffffff));
> >> fh[4] = cpu_to_le32(generation);
> >>
> >> if (connectable && !S_ISDIR(inode->i_mode)) {
> >> struct inode *parent;
> >>
> >> spin_lock(&dentry->d_lock);
> >>
> >> parent = dentry->d_parent->d_inode;
> >> objectid = BTRFS_I(parent)->location.objectid;
> >> generation = parent->i_generation;
> >>
> >> fh[5] = cpu_to_le32((u32)(objectid >> 32));
> >> fh[6] = cpu_to_le32((u32)(objectid & 0xffffffff));
> >> fh[7] = cpu_to_le32(generation);
> >>
> >> spin_unlock(&dentry->d_lock);
> >>
> >> len += 3;
> >
> > there is no need to take the d_lock here.
> OK. Will remove it. It was done at fs/ocfs2/export.c. So probably i
> thought it was necessary.
>
> <snip>
>
Ahh see this is where me not being familiar with NFS gets me in trouble, you do
need the d_lock in that case. Sorry about that.
Josef
next prev parent reply other threads:[~2008-06-30 15:08 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 [this message]
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
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=20080630150811.GB18866@unused.rdu.redhat.com \
--to=jbacik@redhat.com \
--cc=balajirrao@gmail.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