From: Steve Dickson <SteveD@redhat.com>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: nfsd module refcount is out of control....
Date: Wed, 30 Jan 2008 09:23:31 -0500 [thread overview]
Message-ID: <47A08863.40400@RedHat.com> (raw)
Has anybody noticed that bring up kNFSD (using a 2.6.24 kernel)
causes 17 modules references on nfsd?
# lsmod | grep nfsd
nfsd 201584 17
lockd 60488 2 nfsd
nfs_acl 6656 1 nfsd
auth_rpcgss 39360 1 nfsd
exportfs 7936 1 nfsd
sunrpc 157892 10 nfsd,lockd,nfs_acl,auth_rpcgss
It appears one of the culprits is svc_set_num_threads() since
it does a module_get() for every thread, which seems a bit
excessive imho... What happen to the idea of the first thread
creating the refcount and the last thread removing the
refcount?
Anyways, I don't see any routine removing all those
refcounts. Should something like svc_exit_thread() be
doing the module_put() since svc_set_num_threads did
all those gets? If not, how are all those refcounts
suppose to be removed?
Also, does anybody have clue as to why auth_rpcgss is
being insmod-ed when there are no secure exports
defined?
tia,
steved.
reply other threads:[~2008-01-30 14:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47A08863.40400@RedHat.com \
--to=steved@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox