From: Neil Brown <neilb@suse.de>
To: "Matt Proud" <matt.proud.list@gmail.com>, nfs@lists.sourceforge.net
Subject: Re: Possible causes for rpc.mountd consuming 100 percent CPU.
Date: Mon, 5 Mar 2007 14:25:30 +1100 [thread overview]
Message-ID: <17899.36266.588801.465727@notabene.brown> (raw)
In-Reply-To: message from Neil Brown on Monday March 5
On Monday March 5, neilb@suse.de wrote:
>
> Ho hum. Time to set a bug report off to glibc...
Looks like this has already been fixed.
2005-11-03 Roland McGrath <roland@redhat.com>
[BZ #1548]
* sunrpc/svc.c (svc_getreqset): Use ffsl instead of ffs on fd_mask,
make sure constant is long.
From Jay Lan <jlan@engr.sgi.com>.
So it is fixed in glibc 2.4 and later which SuSE and RH ship, but not
in 2.3.6 which Debian and Ubuntu ship.
I wonder how hard it would be to autodetect the libc version and
include a fix in nfs-utils if an old glibc were in use.....
NeilBrown
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-05 3:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 1:47 Possible causes for rpc.mountd consuming 100 percent CPU Matt Proud
2007-03-05 2:05 ` Neil Brown
2007-03-05 2:12 ` Matt Proud
2007-03-05 3:07 ` Neil Brown
2007-03-05 3:25 ` Neil Brown [this message]
2007-03-05 4:10 ` Neil Brown
[not found] ` <a6a251db0703042017l60a872f7ve93038b169a52968@mail.gmail.com>
[not found] ` <17899.39862.202935.678726@notabene.brown>
2007-03-05 4:32 ` Matt Proud
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=17899.36266.588801.465727@notabene.brown \
--to=neilb@suse.de \
--cc=matt.proud.list@gmail.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