Linux NFS development
 help / color / mirror / Atom feed
From: Fabio Olive Leite <fleite@redhat.com>
To: nfs@lists.sourceforge.net
Subject: Re: [PATCH] Stale NFS negative dentries caused by u32 jiffy wrap
Date: Thu, 26 Apr 2007 00:24:59 -0300	[thread overview]
Message-ID: <20070426032459.GN10449@sleipnir.redhat.com> (raw)
In-Reply-To: <20070424162645.GD10449@sleipnir.redhat.com>

On Tue, Apr 24, 2007 at 01:26:45PM -0300, Fabio Olive Leite wrote:
> =

> This patch solves an issue found on 32bit architectures, where jiffies
> wrap every 50 days. Since many NFS structures are very long lived and
> the code uses jiffies everywhere for timestamp comparisons, there are
> many places where old data can be considered newer than something
> fresh from the server. This one deals with negative dentries, and I'd
> like to have it discussed in the list for sanity checking.

Please disregard this email and patch. With extra testing, I found out
that time_after and friends are not suited at all to the type of
long-lived timestamp comparisons that the NFS code does. I'll start a
new thread for that.

Regards,
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

      reply	other threads:[~2007-04-26  3:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24 16:26 [PATCH] Stale NFS negative dentries caused by u32 jiffy wrap Fabio Olive Leite
2007-04-26  3:24 ` 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=20070426032459.GN10449@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox