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: Tue, 13 Aug 2013 10:07:15 -0400 From: Benjamin Poirier <benjamin.poirier@...il.com> To: Ariel Elior <ariele@...adcom.com> Cc: Dmitry Kravkov <dmitry@...adcom.com>, "davem@...emloft.net" <davem@...emloft.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Eilon Greenstein <eilong@...adcom.com> Subject: Re: [PATCH net v5 0/5] bnx2x: fixes On 2013/08/13 12:38, Ariel Elior wrote: > > I'm confused. Wasn't "[PATCH net v4 1/6] bnx2x: properly initialize > > statistic counters" supposed to fix a race condition? According to > > earlier communication with Ariel: > > In this issue a race condition at driver startup causes a second > > statistics query to be sent before the first one completes, > > resulting in a firmware assert and a stuck chip. A patch was > > sent upstream fixing this: > > http://patchwork.ozlabs.org/patch/264810/ > > As I explicitly mentioned in the communique which you quoted above, the patch was sent but not yet accepted. > This is precisely the upstream process - patches are being sent, reviewed and sometimes rejected and revised. > If you have further questions please address them to me - the technical forum is no place for this kind of discussion. > Thanks, > Ariel > It's a technical question about a patch which was sent upstream. Where should the discussion happen if not upstream? Let me rephrase my question: I'm confused. I thought that "[PATCH net v4 1/6] bnx2x: properly initialize statistic counters" was meant to fix a race condition at driver startup which causes a second statistics query to be sent before the first one completes, resulting in a firmware assert and a stuck chip. Am I mistaken and there is no such race condition, or is it addressed by the other patches in this series? -- 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