From: Greg Banks <gnb@melbourne.sgi.com>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: David Chinner <dgc@sgi.com>, Bharata B Rao <bharata@in.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] dcache: separate slab for directory dentries
Date: Fri, 07 Oct 2005 13:54:37 +1000 [thread overview]
Message-ID: <1128657277.6710.826.camel@hole.melbourne.sgi.com> (raw)
In-Reply-To: <1128601731.9358.2.camel@kleikamp.austin.ibm.com>
On Thu, 2005-10-06 at 22:28, Dave Kleikamp wrote:
> On Thu, 2005-10-06 at 16:27 +1000, David Chinner wrote:
> > +static struct dentry * d_realloc_for_inode(struct dentry * dentry,
> > + struct inode *inode)
> > +{
> > + int flags = 0;
> > + struct dentry *new;
> > [...]
> > + new = __d_alloc(parent, &dentry->d_name, dentry->d_flags | flags);
> > +
> > + spin_lock(&dcache_lock);
> > +
> > + BUG_ON(new == NULL); /* TODO */
> > + if (new) {
> > +// new->d_op = dentry->d_op;
> > +// new->d_fsdata = dentry->d_fsdata;
> > + }
> > +
> > + return new;
> > +}
>
> Isn't this leaking the original dentry? Shouldn't it be doing a dput or
> at least a d_free here?
While it has been some months since I wrote this, and it was not
intended to be a production patch, I don't believe it leaks dentries.
The function is called on the path real_lookup() to i_op->lookup() to
d_splice_alias(), and the original dentry allocated in real_lookup()
is d_put() there if a non-NULL new dentry pointer is passed back up
via d_splice_alias() and i_op->lookup().
>From the 2.6.5-based tree this patch was developed in:
static struct dentry * real_lookup(struct dentry * parent, struct qstr *
name, struct nameidata *nd)
{
...
struct dentry * dentry = d_alloc(parent, name);
result = ERR_PTR(-ENOMEM);
if (dentry) {
result = dir->i_op->lookup(dir, dentry, nd);
if (result)
dput(dentry);
else
result = dentry;
}
...
}
STATIC struct dentry *
linvfs_lookup(
struct inode *dir,
struct dentry *dentry,
struct nameidata *nd)
{
...
VOP_LOOKUP(vp, dentry, &cvp, 0, NULL, NULL, error);
...
return d_splice_alias(LINVFS_GET_IP(cvp), dentry);
}
Had this been a production patch I might have mentioned this
subtlety in the comments ;-)
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-10-07 3:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 10:57 VM balancing issues on 2.6.13: dentry cache not getting shrunk enough Theodore Ts'o
2005-09-11 12:00 ` Dipankar Sarma
2005-09-12 3:16 ` Theodore Ts'o
2005-09-12 6:16 ` Martin J. Bligh
2005-09-12 12:53 ` Bharata B Rao
2005-09-13 8:47 ` Bharata B Rao
2005-09-13 21:59 ` David Chinner
2005-09-14 9:01 ` Andi Kleen
2005-09-14 9:16 ` Manfred Spraul
2005-09-14 9:43 ` Andrew Morton
2005-09-14 9:52 ` Dipankar Sarma
2005-09-14 22:44 ` Theodore Ts'o
2005-09-14 9:35 ` Andrew Morton
2005-09-14 13:57 ` Martin J. Bligh
2005-09-14 15:37 ` Sonny Rao
2005-09-15 7:21 ` Helge Hafting
2005-09-14 22:48 ` David Chinner
2005-09-14 15:48 ` Sonny Rao
2005-09-14 22:02 ` David Chinner
2005-09-14 22:40 ` Sonny Rao
2005-09-15 1:14 ` David Chinner
2005-10-06 6:27 ` [PATCH] dcache: separate slab for directory dentries David Chinner, gnb
2005-10-06 12:28 ` Dave Kleikamp
2005-10-07 3:54 ` Greg Banks [this message]
2005-10-07 13:00 ` Dave Kleikamp
2005-09-14 21:34 ` VM balancing issues on 2.6.13: dentry cache not getting shrunk enough Marcelo Tosatti
2005-09-14 21:43 ` Dipankar Sarma
2005-09-15 4:28 ` Bharata B Rao
2005-09-14 23:08 ` Marcelo Tosatti
2005-09-15 9:39 ` Bharata B Rao
2005-09-15 13:29 ` Marcelo Tosatti
2005-10-02 16:32 ` Bharata B Rao
2005-10-02 20:06 ` Marcelo
2005-10-04 13:36 ` shrinkable cache statistics [was Re: VM balancing issues on 2.6.13: dentry cache not getting shrunk enough] Bharata B Rao
2005-10-05 21:25 ` Marcelo Tosatti
2005-10-07 8:12 ` Bharata B Rao
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=1128657277.6710.826.camel@hole.melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=bharata@in.ibm.com \
--cc=dgc@sgi.com \
--cc=dipankar@in.ibm.com \
--cc=linux-mm@kvack.org \
--cc=shaggy@austin.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox