From: David Lamparter <equinox@diac24.net>
To: David Miller <davem@davemloft.net>
Cc: equinox@diac24.net, hans.schillstrom@ericsson.com,
netdev@vger.kernel.org, ebiederm@xmission.com
Subject: Re: RFC Hanging clean-up of a namespace
Date: Thu, 19 Jan 2012 22:03:52 +0100 [thread overview]
Message-ID: <20120119210352.GA3347849@jupiter.n2.diac24.net> (raw)
In-Reply-To: <20120119.152752.318442465605898328.davem@davemloft.net>
On Thu, Jan 19, 2012 at 03:27:52PM -0500, David Miller wrote:
> From: David Lamparter <equinox@diac24.net>
> > On Thu, Jan 19, 2012 at 02:31:05PM -0500, David Miller wrote:
> >> Then if a new netns is created that tries to reuse the address used by
> >> the mini-netns which hasn't cleared yet, you give -EAGAIN until all
> >> the timewaits expire.
> >
> > The effect of this is that you end up being unable to reboot lxc based
> > virtualised hosts without waiting 2 minutes for the TCP timers to
> > expire. That sounds completely unacceptable to me.
>
> All you are saying to me is that we are on a trajectory to major problems
> if it becomes pervasive that time-wait gets cancelled out and addresses
> then get reused so quickly.
On the funny side, RFC 793 page 28 actually states under "Knowing When
to Keep Quiet" that
"To be sure that a TCP does not create a segment that carries a
sequence number which may be duplicated by an old segment remaining in
the network, the TCP must keep quiet for a maximum segment lifetime
(MSL) before assigning any sequence numbers upon starting up or
recovering from a crash in which memory of sequence numbers in use was
lost. For this specification the MSL is taken to be 2 minutes."
Let's implement that, I bet people will love a 2 minute wait on TCP
connections after booting :-)
-David
next prev parent reply other threads:[~2012-01-19 21:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 11:07 RFC Hanging clean-up of a namespace Hans Schillstrom
2012-01-19 13:31 ` David Lamparter
2012-01-19 17:40 ` David Miller
2012-01-19 19:01 ` David Lamparter
2012-01-19 19:06 ` David Miller
2012-01-19 19:25 ` David Lamparter
2012-01-19 19:31 ` David Miller
2012-01-19 19:53 ` David Lamparter
2012-01-19 20:27 ` David Miller
2012-01-19 21:03 ` David Lamparter [this message]
2012-01-19 21:24 ` Eric W. Biederman
2012-01-19 21:40 ` David Lamparter
2012-01-19 21:40 ` Hagen Paul Pfeifer
2012-01-19 21:47 ` David Lamparter
2012-01-19 22:10 ` Rick Jones
2012-01-19 22:16 ` Hagen Paul Pfeifer
2012-01-19 22:37 ` David Miller
2012-01-20 6:08 ` Hans Schillstrom
2012-01-20 10:08 ` Eric W. Biederman
2012-01-20 11:51 ` Hans Schillstrom
2012-01-20 20:55 ` Eric W. Biederman
2012-01-23 6:07 ` Hans Schillstrom
2012-01-23 6:25 ` Eric W. Biederman
2012-01-23 6:58 ` Hans Schillstrom
2012-01-23 7:17 ` Eric W. Biederman
2012-01-23 7:30 ` Hans Schillstrom
2012-01-23 7:55 ` Eric W. Biederman
2012-01-19 19:40 ` Hans Schillström
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=20120119210352.GA3347849@jupiter.n2.diac24.net \
--to=equinox@diac24.net \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=hans.schillstrom@ericsson.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).