mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Forrest <forrest@lmcg.wisc.edu>
To: linux-kernel@vger.kernel.org
Subject: lockd hanging
Date: Thu, 11 Apr 2002 18:33:20 -0500 (CDT)	[thread overview]
Message-ID: <200204112333.SAA22343@radium.lmcg.wisc.edu> (raw)

This is my first post to this list, I'll try to be brief.

Kernel version 2.4.18.

Problem: under heavy load (i.e. >32 client machines locking/unlocking
the same NFS mounted file repeatedly) lockd hangs (sometimes hanging
the local file system with it) and the server must be rebooted.

I have discovered a basic flaw in the lockd code and have patched it
to work correctly.  Is there an individual who is "responsible" for
the lockd code whom I can correspond with to discuss the flaws I
have found, the solutions I have devised, and how to get this patch
into general circulation.

P.S. I have examined the lockd code up to version 2.5.7 and it has not
     changed in any significant way since 2.4.18.

-- 
+----------------------------------+----------------------------------+
| Daniel K. Forrest                | Laboratory for Molecular and     |
| forrest@lmcg.wisc.edu            | Computational Genomics           |
| (608)262-9479                    | University of Wisconsin, Madison |
+----------------------------------+----------------------------------+

             reply	other threads:[~2002-04-11 23:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11 23:33 Daniel Forrest [this message]
2002-04-12  7:10 ` Trond Myklebust
2002-04-24 21:13   ` Daniel Forrest
2002-04-26  8:30     ` Trond Myklebust
2002-04-26 17:25       ` Daniel Forrest

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=200204112333.SAA22343@radium.lmcg.wisc.edu \
    --to=forrest@lmcg.wisc.edu \
    --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

all inboxes | Powered by JetHome®