Bug 1900 - RPC servers freeze in competetive TCP calls containing large data
RPC servers freeze in competetive TCP calls containing large data
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-03-31 03:08 EST by olli.saarela
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-07-28 01:16:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description olli.saarela 1999-03-31 03:08:41 EST
Function readtcp() in sunrpc/svc_tcp.c has recently(?) been
optimized for situations with competetive client calls. This
optimization fails when the clients send large data items to
the client. ("Large" probably meaning data which RPC has
split to several read() blocks, in our case, a struct with
arrays of several thousand double elements).

When readtcp() is reverted back to the old version,
everything works well again. (= call to svc_getreqset() is
removed and readfds=svc_fdset; is replaced by
Comment 1 Preston Brown 1999-03-31 17:50:59 EST
this could be nasty.
Comment 2 Cristian Gafton 1999-07-09 18:21:59 EDT
Is this bug still valid?
Can we have a test case for the failure?

For now, "it works for me". The glibc-2.1.2-1 package that will be
available from rawhide shortly does include a number of RPC fixed. Can
you also test that?
Comment 3 olli.saarela 1999-07-19 03:51:59 EDT
The glibc-2.1.2-1 package has fixed this bug. I wrote a test case (5
files, 10 kB), and can provide it to anyone interested.

I don't want to "Reopen bug", but there is no way to unchek it from
the radio button below.
Comment 4 Cristian Gafton 1999-07-28 01:16:59 EDT
Fixed in glibc-2.1.2-1 and later.

Note You need to log in before you can comment on or make changes to this bug.