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: Wed, 21 Apr 2010 09:33:56 -0500 From: Timur Tabi <timur.tabi@...il.com> To: Kumar Gala <galak@...nel.crashing.org> Cc: David Miller <davem@...emloft.net>, afleming@...escale.com, netdev@...r.kernel.org Subject: Re: [PATCH] gianfar: Wait for both RX and TX to stop On Wed, Apr 21, 2010 at 7:17 AM, Kumar Gala <galak@...nel.crashing.org> wrote: > I understand, its more a sense that we are saying we want to time out for what I consider a catastrophic HW failure. And how else will you detect and recover from such a failure without a timeout? And are you absolutely certain that there will never be a programming failure that will cause this loop to spin forever? If you're really opposed to a timeout, you can still use spin_event_timeout() by just setting the timeout to -1 and adding a comment explaining why. -- Timur Tabi Linux kernel developer at Freescale -- 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