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
| ||
|
Message-Id: <201207270536.50292.s.L-H@gmx.de> Date: Fri, 27 Jul 2012 05:36:45 +0200 From: "Stefan Lippers-Hollmann" <s.L-H@....de> To: Francois Romieu <romieu@...zoreil.com> Cc: Eric Dumazet <eric.dumazet@...il.com>, David Miller <davem@...emloft.net>, hayeswang@...ltek.com, netdev@...r.kernel.org, Alex Villacís Lasso <a_villacis@...osanto.com>, Josh Boyer <jwboyer@...hat.com>, Tom Herbert <therbert@...gle.com> Subject: Re: [PATCH] r8169: revert "add byte queue limit support". Hi On Tuesday 24 July 2012, Francois Romieu wrote: > Eric Dumazet <eric.dumazet@...il.com> : > > On Mon, 2012-07-23 at 22:55 +0200, Francois Romieu wrote: > > > This reverts commit 036dafa28da1e2565a8529de2ae663c37b7a0060. > [...] > > bisection is not always the right way to qualify a problem. > > I know. At some point I switch from "I could search more" to "users situation > will improve in a definite timeframe". > > > BQL in itself had some fixes coming _after_ commit 036dafa28da1e2565 > > Thanks. > > They are in stable as of 3.4.5: […] > I have obviously not directed users at them and I do not see any > of the victims using a non -stable / -vendor or recent enough > kernel to test this patch since the issue has been reported. > > They are both worth testing. […] 3.4.x up to and including 3.4.4 exposed the problem on these cards[1]: r8169 0000:04:00.0: eth0: RTL8168d/8111d at 0xffffc90000c72000, 00:24:1d:72:7c:75, XID 081000c0 IRQ 44 r8169 0000:05:00.0: eth1: RTL8168d/8111d at 0xffffc90000c70000, 00:24:1d:72:7c:77, XID 081000c0 IRQ 45 while it is stable with "add byte queue limit support" reverted; 3.4.5+ was only tested with 036dafa28da1e2565a8529de2ae663c37b7a0060 reverted. Now testing plain 3.5.0, which still includes it, has been reliable for almost 3 days - while the issue usually triggered within one hour (3 hours at most) in 3.4.[0-4]. It might be a little too early to give a definitive answer, but so far r8169/ 3.5.0 looks positive. Regards Stefan Lippers-Hollmann [1] Message-Id: <201206290131.49150.s.L-H@....de> http://lkml.kernel.org/r/<201206290131.49150.s.L-H@....de> -- 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
Powered by blists - more mailing lists