| 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, 20 Mar 2009 17:00:07 -0700 (PDT) From: David Miller <davem@...emloft.net> To: rdreier@...co.com Cc: drifter@...oft.de, netdev@...r.kernel.org Subject: Re: e1000 under VMware doesn't work since 2.6.27.16 - BISECTED From: David Miller <davem@...emloft.net> Date: Fri, 20 Mar 2009 16:55:16 -0700 (PDT) > From: Roland Dreier <rdreier@...co.com> > Date: Fri, 20 Mar 2009 16:03:58 -0700 > > > > > we're using virtual machines under VMware with the e1000 emulated > > > > network card. > > > > > Sounds like vmware doesn't emulate the e1000 accurately enough. > > > > I would consider problems with the vmware emulated e1000 to be similar > > to hardware quirks in some other chip rev supported by the e1000 > > driver. If a driver change broke e1000 inside a vmware VM then we > > should probably fix the kernel if possible (although vmware probably > > wants to improve their emulation too). > > If such a "fix" would be to the detriment of real actual hardware, > this logic doesn't hold. > > The same applies to cases like qemu as well. And I want to amend this to state that I emphatically do not think that a driver maintainer is on the hook to be compatible with all the software emulators out there. That's rediculious. Keeping up with the problems on real hardware is difficult enough. At the very least the software emulators can be fixed easily, whereas real hardware not so much. -- 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