From: Al Viro <viro@ZenIV.linux.org.uk>
To: Maxim Patlasov <mpatlasov@parallels.com>
Cc: ebiederm@xmission.com, linux-kernel@vger.kernel.org,
dhowells@redhat.com, akpm@linux-foundation.org,
fengguang.wu@intel.com, devel@openvz.org
Subject: Re: [PATCH] proc: avoid extra pde_put() in proc_fill_super()
Date: Wed, 23 Jan 2013 16:17:15 +0000 [thread overview]
Message-ID: <20130123161715.GX4939@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130122170100.11323.13045.stgit@maximpc.sw.ru>
On Tue, Jan 22, 2013 at 09:03:26PM +0400, Maxim Patlasov wrote:
> If proc_get_inode() succeeded, but d_make_root() failed, pde_put() for
> proc_root will be called twice: the first time due to iput() called from
> d_make_root() and the second time directly in the end of proc_fill_super().
I don't like that solution, TBH. How about making proc_get_inode() call
pde_put() on failure instead? Note that it already does so if inode had
been found in icache, so this will just make the refcounting consistent.
Completely untested patch follows:
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---
diff --git a/fs/proc/generic.c b/fs/proc/generic.c
index 76ddae8..8b487e5 100644
--- a/fs/proc/generic.c
+++ b/fs/proc/generic.c
@@ -413,31 +413,24 @@ struct dentry *proc_lookup_de(struct proc_dir_entry *de, struct inode *dir,
struct dentry *dentry)
{
struct inode *inode = NULL;
- int error = -ENOENT;
spin_lock(&proc_subdir_lock);
for (de = de->subdir; de ; de = de->next) {
if (de->namelen != dentry->d_name.len)
continue;
- if (!memcmp(dentry->d_name.name, de->name, de->namelen)) {
- pde_get(de);
- spin_unlock(&proc_subdir_lock);
- error = -ENOMEM;
- inode = proc_get_inode(dir->i_sb, de);
- goto out_unlock;
- }
- }
- spin_unlock(&proc_subdir_lock);
-out_unlock:
-
- if (inode) {
+ if (memcmp(dentry->d_name.name, de->name, de->namelen))
+ continue;
+ pde_get(de);
+ spin_unlock(&proc_subdir_lock);
+ inode = proc_get_inode(dir->i_sb, de);
+ if (!inode)
+ return ERR_PTR(-ENOMEM);
d_set_d_op(dentry, &proc_dentry_operations);
d_add(dentry, inode);
return NULL;
}
- if (de)
- pde_put(de);
- return ERR_PTR(error);
+ spin_unlock(&proc_subdir_lock);
+ return ERR_PTR(-ENOENT);
}
struct dentry *proc_lookup(struct inode *dir, struct dentry *dentry,
diff --git a/fs/proc/inode.c b/fs/proc/inode.c
index 439ae688..e2bbe20 100644
--- a/fs/proc/inode.c
+++ b/fs/proc/inode.c
@@ -448,9 +448,7 @@ struct inode *proc_get_inode(struct super_block *sb, struct proc_dir_entry *de)
struct inode * inode;
inode = iget_locked(sb, de->low_ino);
- if (!inode)
- return NULL;
- if (inode->i_state & I_NEW) {
+ if (inode && inode->i_state & I_NEW) {
inode->i_mtime = inode->i_atime = inode->i_ctime = CURRENT_TIME;
PROC_I(inode)->pde = de;
@@ -499,6 +497,5 @@ int proc_fill_super(struct super_block *s)
return 0;
printk("proc_read_super: get root inode failed\n");
- pde_put(&proc_root);
return -ENOMEM;
}
next prev parent reply other threads:[~2013-01-23 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 17:03 [PATCH] proc: avoid extra pde_put() in proc_fill_super() Maxim Patlasov
2013-01-23 16:17 ` Al Viro [this message]
2013-01-24 12:08 ` Maxim Patlasov
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=20130123161715.GX4939@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=devel@openvz.org \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatlasov@parallels.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.