public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "H . J . Lu" <hjl@lucon.org>
Cc: nfs@lists.sourceforge.net,
	linux kernel <linux-kernel@vger.kernel.org>,
	alan@redhat.com
Subject: Re: [NFS] Has anyone run the Connectathon Testsuite recently?
Date: 22 Oct 2001 10:28:18 +0200	[thread overview]
Message-ID: <shshess6pul.fsf@charged.uio.no> (raw)
In-Reply-To: <20011021232452.A2473@lucon.org>
In-Reply-To: "H . J . Lu"'s message of "Sun, 21 Oct 2001 23:24:52 -0700"

>>>>> " " == hjl  <H> writes:

     > I checked out kernel 2.4.9-6 from RedHat 7.1 updates. It failed
     > the Connectathon Testsuite against the Linux and none-Linux
     > server. I believe both NFS server and client are broken in
     > 2.4.9-6. See

     > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=54868

     > Now the question is how bad the current Linus/AC kernels are?


They are not affected. The RedHat kernel seems to have the (known) bug
in which the grace period isn't reset. My fault for introducing it in
the 2.4.9-ac series...

I haven't gotten round to syncing up the AC kernel to the full reclaim
code that's in Linus' kernel, but Alan has already applied the
following patch (as of 2.4.10-ac12).

Cheers,
  Trond

--- linux-2.4.9-6/fs/lockd/svc.c.orig	Thu Oct 18 15:00:46 2001
+++ linux-2.4.9-6/fs/lockd/svc.c	Mon Oct 22 10:25:21 2001
@@ -122,6 +122,15 @@
 			if (nlmsvc_ops) {
 				nlmsvc_ops->detach();
 				grace_period_expire = nlmsvc_grace_period + jiffies;
+#ifdef RPC_DEBUG
+				nlmsvc_grace_period = 10 * HZ;
+#else
+				if (nlm_grace_period)
+					nlmsvc_grace_period = ((nlm_grace_period + nlm_timeout - 1)
+								/ nlm_timeout) * nlm_timeout * HZ;
+				else
+					nlmsvc_grace_period = 5 * nlm_timeout * HZ;
+#endif
 			}
 		}
 
@@ -133,8 +142,10 @@
 		 */
 		if (!grace_period_expire) {
 			timeout = nlmsvc_retry_blocked();
-		} else if (time_before(grace_period_expire, jiffies))
+		} else if (time_before(grace_period_expire, jiffies)) {
 			grace_period_expire = 0;
+			nlmsvc_grace_period = 0;
+		}
 
 		/*
 		 * Find a socket with data available and call its


      parent reply	other threads:[~2001-10-22  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22  6:24 Has anyone run the Connectathon Testsuite recently? H . J . Lu
2001-10-22  7:54 ` Alan Cox
2001-10-22  8:28 ` 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=shshess6pul.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=alan@redhat.com \
    --cc=hjl@lucon.org \
    --cc=linux-kernel@vger.kernel.org \
    --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