From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chuck Lever <chucklever@gmail.com>
Cc: Frank van Maarseveen <frankvm@frankvm.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Mohit Katiyar <katiyar.mohit@gmail.com>,
Linux NFS mailing list <nfs@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [NFS] NFS inconsistent behaviour
Date: Thu, 19 Oct 2006 13:11:17 +0100 [thread overview]
Message-ID: <1161259878.17335.35.camel@localhost.localdomain> (raw)
In-Reply-To: <76bd70e30610181317w3e8315e5m75056305904a1bce@mail.gmail.com>
Ar Mer, 2006-10-18 am 16:17 -0400, ysgrifennodd Chuck Lever:
> Some discussion on both FreeBSD and Linux mailing lists suggests that
> ignoring TIME_WAIT has some risk to it, so that may not be an
Ignoring time wait leads to corrupted sessions and can lead to tcp food
fights. It exists for a reason although the protocol itself actually
does still have flaws in this area (which are kept in the locked
cupboard full of skeletons at the IETF 8) )
Alan
next prev parent reply other threads:[~2006-10-19 12:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A93BD15112CD05479B1CD204F7F1D4730513DB@exch-04.noida.hcltech.com>
2006-10-16 7:13 ` NFS inconsistent behaviour Mohit Katiyar
2006-10-16 8:46 ` Frank van Maarseveen
2006-10-16 9:35 ` Mohit Katiyar
2006-10-16 9:39 ` Frank van Maarseveen
2006-10-18 1:22 ` Mohit Katiyar
2006-10-18 6:39 ` Frank van Maarseveen
2006-10-18 17:57 ` Trond Myklebust
2006-10-18 18:37 ` Trond Myklebust
2006-10-18 18:38 ` Frank van Maarseveen
2006-10-18 19:26 ` Trond Myklebust
2006-10-18 20:09 ` [NFS] " Frank van Maarseveen
2006-10-18 20:17 ` Chuck Lever
2006-10-18 20:44 ` Trond Myklebust
2006-10-19 12:11 ` Alan Cox [this message]
2006-10-19 1:53 ` Mohit Katiyar
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=1161259878.17335.35.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=chucklever@gmail.com \
--cc=frankvm@frankvm.com \
--cc=katiyar.mohit@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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