From: Jeff Layton <jlayton@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: [PATCH 2/2] rpc_pipe: set dentry operations at d_alloc time
Date: Tue, 25 Jun 2013 07:00:56 -0400 [thread overview]
Message-ID: <20130625070056.6a507da0@corrin.poochiereds.net> (raw)
In-Reply-To: <1372122340-28982-3-git-send-email-jlayton@redhat.com>
On Mon, 24 Jun 2013 21:05:40 -0400
Jeff Layton <jlayton@redhat.com> wrote:
> Currently the way these get set is a little convoluted. If the dentry is
> allocated via lookup from userland, then it gets set by simple_lookup.
> If it gets allocated when the kernel is populating the directory, then
> it gets set via __rpc_lookup_create_exclusive, which has to check
> whether they might already be set. Between both of these, this ensures
> that all dentries have their d_op pointer set.
>
> Instead of doing that, just have them set at d_alloc time by pointing
> sb->s_d_op at them. With that change, we no longer want the lookup op
> to set them, so we must move to using our own lookup routine.
>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
> net/sunrpc/rpc_pipe.c | 25 ++++++++++++++++++++-----
> 1 file changed, 20 insertions(+), 5 deletions(-)
>
> diff --git a/net/sunrpc/rpc_pipe.c b/net/sunrpc/rpc_pipe.c
> index 99cd7db..7b471a2 100644
> --- a/net/sunrpc/rpc_pipe.c
> +++ b/net/sunrpc/rpc_pipe.c
> @@ -471,6 +471,23 @@ struct rpc_filelist {
> umode_t mode;
> };
>
> +/*
> + * Lookup the data. This is trivial - if the dentry didn't already
> + * exist, we know it is negative.
> + */
> +static struct dentry *
> +rpc_lookup(struct inode *dir, struct dentry *dentry, unsigned int flags)
> +{
> + if (dentry->d_name.len > NAME_MAX)
> + return ERR_PTR(-ENAMETOOLONG);
> + d_add(dentry, NULL);
> + return NULL;
> +}
> +
> +const struct inode_operations rpc_dir_inode_operations = {
> + .lookup = rpc_lookup,
> +};
> +
Nit: the above should probably be static. Let me know if you want me to respin...
> static struct inode *
> rpc_get_inode(struct super_block *sb, umode_t mode)
> {
> @@ -483,7 +500,7 @@ rpc_get_inode(struct super_block *sb, umode_t mode)
> switch (mode & S_IFMT) {
> case S_IFDIR:
> inode->i_fop = &simple_dir_operations;
> - inode->i_op = &simple_dir_inode_operations;
> + inode->i_op = &rpc_dir_inode_operations;
> inc_nlink(inode);
> default:
> break;
> @@ -657,11 +674,8 @@ static struct dentry *__rpc_lookup_create_exclusive(struct dentry *parent,
> if (!dentry)
> return ERR_PTR(-ENOMEM);
> }
> - if (dentry->d_inode == NULL) {
> - if (!dentry->d_op)
> - d_set_d_op(dentry, &simple_dentry_operations);
> + if (dentry->d_inode == NULL)
> return dentry;
> - }
> dput(dentry);
> return ERR_PTR(-EEXIST);
> }
> @@ -1108,6 +1122,7 @@ rpc_fill_super(struct super_block *sb, void *data, int silent)
> sb->s_blocksize_bits = PAGE_CACHE_SHIFT;
> sb->s_magic = RPCAUTH_GSSMAGIC;
> sb->s_op = &s_ops;
> + sb->s_d_op = &simple_dentry_operations;
> sb->s_time_gran = 1;
>
> inode = rpc_get_inode(sb, S_IFDIR | S_IRUGO | S_IXUGO);
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2013-06-25 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 1:05 [PATCH 0/2] rpc_pipe: clean up how dentry operations get set in rpc_pipefs Jeff Layton
2013-06-25 1:05 ` [PATCH 1/2] rpc_pipe: export simple_dentry_operations and have rpc_pipefs use it Jeff Layton
2013-06-25 15:36 ` Myklebust, Trond
2013-07-01 16:22 ` Jeff Layton
2013-07-02 15:29 ` Jeff Layton
2013-06-25 1:05 ` [PATCH 2/2] rpc_pipe: set dentry operations at d_alloc time Jeff Layton
2013-06-25 11:00 ` Jeff Layton [this message]
2013-07-02 17:00 ` [PATCH v2] " Jeff Layton
2013-07-14 14:00 ` Al Viro
2013-07-15 10:43 ` Jeff Layton
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=20130625070056.6a507da0@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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).