From: Michael Schroeder <mls@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Olaf Kirch <okir@suse.de>, nfs@lists.sourceforge.net
Subject: Re: [PATCH NFSv2] Drop inode after rename
Date: Mon, 11 Jul 2005 14:28:18 +0200 [thread overview]
Message-ID: <20050711122818.GA19562@suse.de> (raw)
In-Reply-To: <1121082965.8204.42.camel@lade.trondhjem.org>
On Mon, Jul 11, 2005 at 07:56:05AM -0400, Trond Myklebust wrote:
> ...but it should be unnecessary.
>
> d_delete() is supposed to cause the inode to be dropped: if it cannot
> immediately iput the inode, it will drop the dentry. So unless there
> exists a hard link or an aliased dentry, the inode should get dropped
> and freed pretty rapidly.
AFAIR the problem is that i_nlink doesn't get decremented and
therefore the inode doesn't get deleted.
Cheers,
Michael.
--
Michael Schroeder mls@suse.de
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-07-11 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 10:46 [PATCH NFSv2] Drop inode after rename Olaf Kirch
2005-07-11 10:50 ` Olaf Kirch
2005-07-11 11:05 ` Trond Myklebust
2005-07-11 11:07 ` Olaf Kirch
2005-07-11 11:14 ` Trond Myklebust
2005-07-11 11:24 ` Olaf Kirch
2005-07-11 11:56 ` Trond Myklebust
2005-07-11 12:28 ` Michael Schroeder [this message]
2005-07-11 12:34 ` Trond Myklebust
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=20050711122818.GA19562@suse.de \
--to=mls@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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.