Re: Linux 2.4.32-rc2

[Roberto Nibali <ratz@drugphish.ch>]

Salut Willy,

>>I will send a proper signed-off and acked-by patch against rc2 after
>>some more stress testing. So, please hold off releasing until then. I'm
>>done testing this piece of code by tomorrow noon (GMT+1).
> 
> OK, fine. I'll merge it into next -hf (probably within a few days). Please
> insist loudly if you consider it important to fix quickly because it's a
> real regression, as I don't want to have people wait for long if one hotfix
> causes trouble.

It is absolutely needed. Without it, people will really experience a
long term problem with hanging templates in IPVS, manifesting itself
depending on time and hardware configuration. So I insist that you merge
this patch _NOW_ :).

I'm checking another issue with an asymmetric reference counting which
is not a bug per se (so far) but could serve you with a plate of
unwelcome surprises in the long run as well. This, however is
post-2.4.32 material because I need a couple of 1000s test runs to check
all invariants and configurations.

> OK, if it was your only concern, then I can say that it compiles and
> runs on x86.

Perfect, thanks.

>>You would need to test IPVS on a SMP box using persistent setup and 0
>>port feature and the expire_nodest_conn proc-fs entry set to 1. Hit the
>>LB with 100Mbit/s traffic balancing it on 2-3 RS and reload the
>>configuration using ipvsadm, _but_ without rmmod'ing the ip_vs_* kernel
>>modules. Set the persistency timeout low (60 secs) and the
>>timeout_finwait to 10*HZ. You need 2 clients which connect over a Linux
>>router to a LVS_DR setup, one needs to be router through and the other
>>should be NAT'd on the Linux router using a NAT pool to simulate 100's
>>of clients. This way you have the slashdot-hype and the AOL proxy boost
>>hitting your LB and generating loaded persistency templates which will
>>then hit the code in question, wenn the internal timer expires. You need
>>to grep for NONE in ipvsadm -L -n -c to get the template entries. You
>>must stop the client connecting directly through the Linux router after
>>you reloaded the LB setup and then you observe the persistent template
>>created for this client until the timer expires. Then you start it again
>>and with luck you should see the abberant behaviour of a missed
>>__ip_vs_conn_put(cp) :). I am pretty sure you do not want to go through
>>this setup. I have it here and I'm stress testing all possible
>>combinations of this szenario.
>
> Of course this is not the easiest setup just to chase a bug down. But with
> such an explanation, a good manual on IPVS, and a lot of spare time, it
> could be done if it was the only solution. But I'm not willing to spend
> so much time on this yet :-)

I understand. It took me one week to set this up. Reading the code alone
only made me suspicious.

Have a nice day,
Roberto Nibali, ratz
-- 
-------------------------------------------------------------
addr://Kasinostrasse 30, CH-5001 Aarau tel://++41 62 823 9355
http://www.terreactive.com             fax://++41 62 823 9356
-------------------------------------------------------------
terreActive AG                       Wir sichern Ihren Erfolg
-------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/