From: Andrei Warkentin <awarkentin@vmware.com>
To: linux-nfs@vger.kernel.org
Subject: Race between NFS server thread increase / decrease
Date: Mon, 26 Nov 2012 13:49:57 -0800 (PST) [thread overview]
Message-ID: <864189844.31754280.1353966597599.JavaMail.root@vmware.com> (raw)
In-Reply-To: <477254919.31693823.1353963259597.JavaMail.root@vmware.com>
Hi NFSD developers,
I've found what I think is an interesting problem that occurs on single-CPU machines as far as I can tell.
Basically the following snippet will occasionally loop forever printing that one thread is still running. Further
attempts to run "/usr/sbin/rpc.nfsd 0" don't help.
/usr/sbin/rpc.nfsd 1
/usr/sbin/rpc.nfsd 0
while [ ! $[`cat /proc/fs/nfsd/threads`] -eq 0 ]; do
echo $[`cat /proc/fs/nfsd/threads`] still running
sleep .1
done
I've not looked a whole lot at it. It appears that although the paths calling svc_set_num_threads synchronize on nfsd_mutex, the code doesn't seem to try waiting on the number of threads to reach the desired count.
What do you guys think?
Thanks.
A
next parent reply other threads:[~2012-11-26 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <477254919.31693823.1353963259597.JavaMail.root@vmware.com>
2012-11-26 21:49 ` Andrei Warkentin [this message]
2012-11-28 14:57 ` Race between NFS server thread increase / decrease J. Bruce Fields
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=864189844.31754280.1353966597599.JavaMail.root@vmware.com \
--to=awarkentin@vmware.com \
--cc=linux-nfs@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 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.