From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Frank Cusack <fcusack@fcusack.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4 v. 2.5 nfs_dentry_iput()
Date: 02 Jun 2003 21:52:05 +0200 [thread overview]
Message-ID: <shsy90kb6l6.fsf@charged.uio.no> (raw)
In-Reply-To: <20030602021529.A19114@google.com>
>>>>> " " == Frank Cusack <fcusack@fcusack.com> writes:
> Hi, Could someone quickly explain the difference between the
> 2.4.20 and 2.5.69 nfs_dentry_iput()?
> static void nfs_dentry_iput(struct dentry *dentry, struct inode
> *inode) {
> if (dentry->d_flags & DCACHE_NFSFS_RENAMED) {
> lock_kernel();
> inode-> i_nlink--; /* only in 2.5 */
Should eventually go into 2.4.x. Not critical...
> nfs_complete_unlink(dentry); unlock_kernel();
> } if (is_bad_inode(inode)) /* not in 2.5 */
> force_delete(inode); /* not in 2.5 */
Done in the VFS in 2.5
> /* When creating a negative dentry, we want to renew
> d_time */ nfs_renew_times(dentry); /* only in 2.5 */
Only needed for the new CTO code in 2.5.
> iput(inode);
> }
Cheers,
Trond
prev parent reply other threads:[~2003-06-02 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 9:15 2.4 v. 2.5 nfs_dentry_iput() Frank Cusack
2003-06-02 19:52 ` Trond Myklebust [this message]
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=shsy90kb6l6.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=fcusack@fcusack.com \
--cc=linux-kernel@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