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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 14 Sep 2007 14:31:17 -0400 From: Dan Williams <dcbw@...hat.com> To: Jeff Garzik <jeff@...zik.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, netdev@...r.kernel.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: [git patches] net driver fixes On Fri, 2007-09-14 at 14:17 -0400, Jeff Garzik wrote: > Dan Williams wrote: > > WTF? why would the default be to _not_ propagate carrier state? Are > > there some mitigating circumstances that require this driver to not > > notify the stack of carrier on/off? Userspace stuff really should know > > about the carrier state, and this disables it by default. > > > The commit explains that... I admit that I probably don't understand the system architecture of where ehea would be used, but would this cause /sys/class/net/ethX/carrier to be TRUE even if the device has no carrier? That seems quite wrong IMHO. When does ehea not have a carrier? And in that case, does sysfs say 1 or 0 for the carrier? Dan - 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