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
| ||
|
Date: Fri, 18 May 2012 02:12:02 +0200 From: Samuel Thibault <samuel.thibault@...-lyon.org> To: "Brandeburg, Jesse" <jesse.brandeburg@...el.com> Cc: "Dave, Tushar N" <tushar.n.dave@...el.com>, "Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>, "Allan, Bruce W" <bruce.w.allan@...el.com>, "Wyborny, Carolyn" <carolyn.wyborny@...el.com>, "Skidmore, Donald C" <donald.c.skidmore@...el.com>, "Rose, Gregory V" <gregory.v.rose@...el.com>, "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>, "Duyck, Alexander H" <alexander.h.duyck@...el.com>, "Ronciak, John" <john.ronciak@...el.com>, "David S. Miller" <davem@...emloft.net>, Jiri Pirko <jpirko@...hat.com>, Dean Nelson <dnelson@...hat.com>, "e1000-devel@...ts.sourceforge.net" <e1000-devel@...ts.sourceforge.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] e1000: Reset rx ring index on receive overrun Brandeburg, Jesse, le Thu 17 May 2012 17:04:04 -0700, a écrit : > On Thu, 17 May 2012, Samuel Thibault wrote: > > > Samuel Thibault, le Fri 18 May 2012 01:28:21 +0200, a écrit : > > > Dave, Tushar N, le Thu 17 May 2012 23:22:31 +0000, a écrit : > > > > I am interested in to see if you have actual test case and more > > > > importantly test data that shows that kernel and device indexes are > > > > not synchronized any more. > > > > > > Well, it's not with an actual physical device, but with the kvm > > > emulation. > > > > BTW, it also happens easily when request_irq takes some time to > > complete: since we enable E1000_TCTL_EN before that, the card can have > > time to fill the ring before irqs are processed. > > I think there may well be a bug in the implementation in kvm. The > hardware doesn't have this bug. How does it avoid filling the ring? What is the purpose of the RXO flag if it does avoid them? Samuel -- 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