Message-ID: <43DD144C.9010709@drugphish.ch>
Date: Sun, 29 Jan 2006 20:15:24 +0100
From: Roberto Nibali <ratz@drugphish.ch>
User-Agent: Thunderbird 1.4 (X11/20050908)
MIME-Version: 1.0
To: Willy Tarreau <wtarreau@exosec.fr>
Cc: linux-kernel@vger.kernel.org, Syed Ahemed <kingkhan@gmail.com>,
       Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
       Grant Coady <grant_lkml@dodo.com.au>
Subject: Re: [ANNOUNCE] Linux 2.4.32-hf32.2
References: <20060129175647.GA21999@exosec.fr>
In-Reply-To: <20060129175647.GA21999@exosec.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1412
Lines: 32

Hi Willy,

> Changelog from 2.4.32-hf32.1 to 2.4.32-hf32.2

Which of those are you going to push to Marcelo for inclusion?

I've found two subtle IPVS bugs (using a persistency setup on SMP 
combined with sharp TCP state transition timeouts), one of which is 
fixed in my tree and has been running in production for over 1 month 
now. The other is still in discussion phase with Horms and Julian Anastasov.

> + 2.4.32-bond_alb-hash-table-corruption-1                (ODonnell, Michael)
> 
>   Our systems have been crashing during testing of PCI HotPlug
>   support in the various networking components. We've faulted in
>   the bonding driver due to a bug in bond_alb.c:tlb_clear_slave().
>   In that routine, the last modification to the TLB hash table is
>   made without protection of the lock, allowing a race that can
>   lead tlb_choose_channel() to select an invalid table element.

This is correct. Funny, It never triggered on my systems, but I only 
have a bonding setup on three SMP systems, probably none of them using ALB.

Thanks for your hard work,
Roberto Nibali, ratz
-- 
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
-
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/