public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roberto Nibali <ratz@drugphish.ch>
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
Date: Sun, 29 Jan 2006 20:15:24 +0100	[thread overview]
Message-ID: <43DD144C.9010709@drugphish.ch> (raw)
In-Reply-To: <20060129175647.GA21999@exosec.fr>

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

  reply	other threads:[~2006-01-29 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29 17:56 [ANNOUNCE] Linux 2.4.32-hf32.2 Willy Tarreau
2006-01-29 19:15 ` Roberto Nibali [this message]
2006-01-29 19:24   ` Willy Tarreau

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=43DD144C.9010709@drugphish.ch \
    --to=ratz@drugphish.ch \
    --cc=grant_lkml@dodo.com.au \
    --cc=kingkhan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=wtarreau@exosec.fr \
    /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