netdev - Re: [Bonding-devel] [E1000-devel] [Bugme-new] [Bug 12570] New: Bonding does not work over e1000e.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bdfc5d6e0903170804m2c3d8d0bra6bdd50dc67971be@mail.gmail.com>
Date:	Tue, 17 Mar 2009 11:04:36 -0400
From:	Andy Gospodarek <andy@...yhouse.net>
To:	Konstantin Khorenko <khorenko@...allels.com>
Cc:	"Graham, David" <david.graham@...el.com>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"devel@...ts.sourceforge.net" <devel@...ts.sourceforge.net>,
	"bonding-devel@...ts.sourceforge.net" 
	<bonding-devel@...ts.sourceforge.net>,
	"bugme-daemon@...zilla.kernel.org" <bugme-daemon@...zilla.kernel.org>
Subject: Re: [Bonding-devel] [E1000-devel] [Bugme-new] [Bug 12570] New: 
	Bonding does not work over e1000e.

On Tue, Mar 17, 2009 at 10:25 AM, Konstantin Khorenko
<khorenko@...allels.com> wrote:
>
> Conclusions: well, the latest kernel with your patches does work, thank you very much, David!
> Now i have to solve my original problem - to make RHEL5-based (2.6.18-x) kernel working.
> At the moment RHEL5 kernel is affected by 2 issues:
> 1) that one which seems to be fixed by updating the testkernel from 2.6.29-r1 up to rc4 + 3 your patches.
> 2) when we break a link, mii status is still reported as "up" in /proc/net/bonding/bond1.
>   (at the same time bonding changes the active slave to the working one correctly).
>
> i understand there were a lot of changes since 2.6.18, but i still want to try not to replace the e1000e driver completely from the latest mainstream kernel, but to backport the set of patches to fix this exact issue.
> Could you please help me pointing the patches that are essential to fix this issue (and probably issue 2)) from your point of view?
>

I'm sure if you opened a new bug at bugzilla.redhat.com to address
this issue someone would be willing to make sure this was fixed.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html