Re: A Question about the 2.4.21 Pathconf patch

[Trond Myklebust <trond.myklebust@fys.uio.no>]

>>>>> " " == Steve Dickson <SteveD@redhat.com> writes:

     > So I'm just curious, why (from a protocol purest standpoint)
     > its not being used... and if it ever was used, what were the
     > results...

Oh... Are you perhaps thinking of the RedHat kernels, which contain a
patch to disable the FSINFO usage? That's Ben LaHaise's decision.

Earlier 2.4.x kernels had a bug in the IPv4 socket layer (in
ip_build_xmit_slow() to be more precise). When using non-blocking
writes, the socket layer would build incomplete sets of fragments,
then quit with an -EAGAIN. This had a disastrous DOS effect on certain
servers which weren't able to cope with the flood of orphaned
fragments.
Instead of waiting for the fix, Ben therefore decided to turn off the
automatic probing of r/wsize, and just make the default 4k.

This patch is not in the standard kernel, since we have a proper fix
for the real problem.

Cheers,
  Trond


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs