From: Fabio Olive Leite <fleite@redhat.com>
To: linux-nfs <nfs@lists.sourceforge.net>
Subject: Re: time_after cannot be used alone by NFS code in 32bit architectures
Date: Tue, 8 May 2007 14:09:07 -0300 [thread overview]
Message-ID: <20070508170907.GA32335@sleipnir.redhat.com> (raw)
In-Reply-To: <1178627674.25317.2.camel@heimdal.trondhjem.org>
On Tue, May 08, 2007 at 08:34:34AM -0400, Trond Myklebust wrote:
> =
> dentry verifiers are always set to the parent directory's
> cache_change_attribute. There is no reason to be testing for
> anything other than equality when we're trying to find out if
> the dentry has been checked since the last time the directory
> was modified.
I think this is exactly the simple fix I was trying to get at, but
couldn't see. Thanks a real lot for taking care of it.
Now, if anyone wants to argument the 1 in 2^32 chance of hitting the
correct millisecond 50 days after the current update... =3D) joking!
Thanks,
F=E1bio
-- =
ex sed lex awk yacc, e pluribus unix, amem
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-05-08 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 4:33 time_after cannot be used alone by NFS code in 32bit architectures Fabio Olive Leite
2007-04-26 6:13 ` Neil Brown
2007-05-01 4:04 ` Ian Kent
2007-05-02 11:52 ` Ian Kent
2007-05-08 2:37 ` Ian Kent
2007-05-08 2:43 ` Ian Kent
2007-05-08 6:19 ` Neil Brown
2007-05-08 8:50 ` Ian Kent
2007-05-08 9:43 ` Ian Kent
2007-05-08 12:34 ` Trond Myklebust
2007-05-08 13:07 ` Ian Kent
2007-05-08 13:18 ` Neil Brown
2007-05-08 17:09 ` Fabio Olive Leite [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=20070508170907.GA32335@sleipnir.redhat.com \
--to=fleite@redhat.com \
--cc=nfs@lists.sourceforge.net \
/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.