public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: Roberto Nibali <ratz@drugphish.ch>,
	linux-kernel@vger.kernel.org, Grant Coady <gcoady@gmail.com>
Subject: Re: Linux-2.4.31-hf8
Date: Mon, 7 Nov 2005 07:32:09 -0200	[thread overview]
Message-ID: <20051107093209.GA15453@logos.cnet> (raw)
In-Reply-To: <20051105075915.GD11266@alpha.home.local>

On Sat, Nov 05, 2005 at 08:59:15AM +0100, Willy Tarreau wrote:
> Hi Roberto, Hi Marcelo,
> 
> On Sat, Nov 05, 2005 at 08:00:37AM +0100, Roberto Nibali wrote:
> > Well, to be honest, Horms just found another IPVS "issue" :). It seems
> > we are getting into reviewing 2.4.x IPVS a bit more closely. The problem
> > is that if you have setups where the persistency timeout is below the
> > IPVS state machine related FIN_WAIT (not TCP state) timeout (currently
> > 2*60*HZ) persistent templates will not be invalidated and the timer gets
> > re-set if a we still have a valid connection entry hashed. I've first
> > noted this somewhat aberrant behaviour in 2.2.x kernels but never got
> > around looking at it too closely because in 2.2.x we had a timer mess.
> > 
> > This issue however is absolutely minor since this buglet has been there
> > for ages already and we never received such a bug report. In fact, it
> > would be quite unusual to set a persistency timeout below fin_wait in a
> > LVS_DR setup for productive environments. And I didn't see it because I
> > set the FIN_WAIT to 10*HZ to relax sockets lingering. We can/will queue
> > it up, together with a small refcnt change for -hf9 and post 2.4.32.
> 
> I have a feeling that we will have a lot of network related fixes post
> 2.4.32 (IPVS, IPv6, mcast...). Marcelo, perhaps it would be a good idea
> to merge them in early 2.4.33-pre1 so that competent users have enough
> time to test them ? 

Definately. Please queue them up Willy, I will apply Roberto's fix and
release another -rc.

Thanks guys

      reply	other threads:[~2005-11-07 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 23:18 Linux-2.4.31-hf8 Willy Tarreau
2005-11-05  7:00 ` Linux-2.4.31-hf8 Roberto Nibali
2005-11-05  7:59   ` Linux-2.4.31-hf8 Willy Tarreau
2005-11-07  9:32     ` Marcelo Tosatti [this message]

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=20051107093209.GA15453@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=gcoady@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ratz@drugphish.ch \
    --cc=willy@w.ods.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