From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>,
Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: nfs_refresh_verifier / nfs_renew_times confusion
Date: Wed, 19 Sep 2007 16:20:56 -0400 [thread overview]
Message-ID: <46F184A8.9050801@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
Hi Trond-
I'm reviewing 2.6.23-rc6 + NFS_ALL to prepare for porting my BKL
elimination patch series. I'm confused by a couple of things I found in
fs/nfs/dir.c.
1.
static int nfs_check_verifier(struct inode *dir, struct dentry *dentry)
{
unsigned long verf;
if (IS_ROOT(dentry))
return 1;
verf = dentry->d_time;
if (nfs_caches_unstable(dir)
|| verf != NFS_I(dir)->cache_change_attribute)
return 0;
return 1;
}
Why use the extra variable "verf" here?
2.
Three functions are defined:
static inline void nfs_set_verifier(struct dentry * dentry, unsigned
long verf)
{
dentry->d_time = verf;
}
static void nfs_refresh_verifier(struct dentry * dentry, unsigned long verf)
{
nfs_set_verifier(dentry, verf);
}
static inline void nfs_renew_times(struct dentry * dentry)
{
dentry->d_time = jiffies;
}
but later in the code I see this sequence several times:
nfs_renew_times(dentry);
nfs_refresh_verifier(dentry, verifier);
as well as this sequence:
nfs_renew_times(dentry);
nfs_set_verifier(dentry, nfs_save_change_attribute(dir));
In both cases, the second call overwrites the dentry's d_time field
which was set to "jiffies" in the first call.
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-09-19 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 20:20 Chuck Lever [this message]
2007-09-19 20:36 ` nfs_refresh_verifier / nfs_renew_times confusion Trond Myklebust
2007-09-19 20:48 ` Chuck Lever
2007-09-19 20:57 ` 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=46F184A8.9050801@oracle.com \
--to=chuck.lever@oracle.com \
--cc=nfs@lists.sourceforge.net \
--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.