| 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: Thu, 12 Nov 2009 13:07:35 -0500 From: Ed Cashin <ecashin@...aid.com> To: shemminger@...tta.com, ecashin@...aid.com, karaluh@...aluh.pl, roel.kluin@...il.com, harvey.harrison@...il.com, bzolnier@...il.com, netdev@...r.kernel.org Subject: Re: [PATCH 04/10] AOE: use rcu to find network device Thanks for the responses. On Thu Nov 12 12:11:12 EST 2009, shemminger@...tta.com wrote: ... > Since it is emulating a block device, why not propgate error back > up the stack like a disk that's offline. The lack of local interfaces to use for AoE might be temporary. For example, the admin might be loading a new network driver, or a new link might go online through which the AoE target can be reached. If AoE command packets are not sent or resent but instead are effectively dropped while there are no local interfaces through which to send, then the AoE commands will timeout through the normal mechanisms, at which time the error will be signaled to the block layer. It will be like normal unreliable ethernet transport. In the common case, I think that's going to be the expected behavior, but a printk would probably still be helpful in case the admin doesn't realize why the AoE device is timing out. -- Ed Cashin <ecashin@...aid.com> http://www.coraid.com/ http://noserose.net/e/ -- 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