From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH-2.4] forcedeth update to 0.50 Date: Wed, 31 May 2006 17:07:09 -0300 Message-ID: <20060531200709.GB3432@dmt> References: <20060530220319.GA6945@w.ods.org> <447D2EA8.8020001@colorfullife.com> <20060531055438.GA9142@w.ods.org> <20060531180545.GA30797@dmt> <447DF38E.3020409@colorfullife.com> <20060531194345.GA11807@w.ods.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Manfred Spraul , netdev@vger.kernel.org, Ayaz Abdulla Return-path: Received: from kanga.kvack.org ([66.96.29.28]:34214 "EHLO kanga.kvack.org") by vger.kernel.org with ESMTP id S1751793AbWEaUGk (ORCPT ); Wed, 31 May 2006 16:06:40 -0400 To: Willy Tarreau Content-Disposition: inline In-Reply-To: <20060531194345.GA11807@w.ods.org> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, May 31, 2006 at 09:43:45PM +0200, Willy Tarreau wrote: > On Wed, May 31, 2006 at 09:50:38PM +0200, Manfred Spraul wrote: > > Marcelo Tosatti wrote: > > > > >Since v2.4.33 should be out RSN, my opinion is that applying the > > >one-liner to fix the bringup problem for now is more prudent.. > > > > > > > > > > > It's attached. Untested, but it should work. Just the relevant hunk from > > the 0.42 patch. > > I will test it tomorrow morning. John might be interested in merging it too, > as I have checked today that RHEL3 was affected by the same problem (rmmod > followed by modprobe). > > > But I would disagree with waiting for 2.3.34 for a full backport: > > 0.30 basically doesn't work, thus the update to 0.50 would be a big step > > forward - it can't be worse that 0.30. > > Seconded ! > Manfred, if you have some corner cases in mind, are aware of anything which > might sometimes break, or have a few experimental patches to try, I'm OK for > a few tests while I have the machine (it's SMP BTW). Alright then - will apply Willy's backport.