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, 20 Jun 2014 06:57:04 +0200 From: Olaf Hering <olaf@...fle.de> To: Haiyang Zhang <haiyangz@...rosoft.com> Cc: davem@...emloft.net, netdev@...r.kernel.org, kys@...rosoft.com, jasowang@...hat.com, linux-kernel@...r.kernel.org, driverdev-devel@...uxdriverproject.org Subject: Re: [PATCH net-next] hyperv: Add handler for RNDIS_STATUS_NETWORK_CHANGE event On Thu, Jun 19, Haiyang Zhang wrote: > The RNDIS_STATUS_NETWORK_CHANGE event is received after the Hyper-V host > sleep or hibernation. We refresh network at this time. > + char *argv[] = { "/etc/init.d/network", "restart", NULL }; What happens if that file does not exist? Dead network in the guest? I tend to think if a VM with PV drivers goes to sleep it has to go through the whole suspend/resume cycle, very much like the "LID closed" event. So I think this and the other fbdev change that is floating around is wrong. Olaf -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists