From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756511AbaHHNqZ (ORCPT ); Fri, 8 Aug 2014 09:46:25 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:54081 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752244AbaHHNqW (ORCPT ); Fri, 8 Aug 2014 09:46:22 -0400 Date: Fri, 8 Aug 2014 06:45:49 -0700 From: Greg KH To: Dexuan Cui Cc: "olaf@aepfle.de" , Richard Weinberger , "netdev@vger.kernel.org" , "jasowang@redhat.com" , "driverdev-devel@linuxdriverproject.org" , Haiyang Zhang , LKML , Thomas Shao , "Yue Zhang (OSTC DEV)" , David Miller Subject: Re: [PATCH] Hyperv: Trigger DHCP renew after host hibernation Message-ID: <20140808134549.GD4427@kroah.com> References: <53CCD6F2.6020909@nod.at> <20140721091851.GA28171@aepfle.de> <20140721.143225.2040366896972949930.davem@davemloft.net> <20140808033220.GB10503@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 08, 2014 at 08:11:20AM +0000, Dexuan Cui wrote: > > From: Greg KH [mailto:gregkh@linuxfoundation.org] > > Sent: Friday, August 8, 2014 11:32 AM > > > Hi Richard and all, > > > > > > IMO the most feasible and need-the-least-change solution may be: > > > the hyperv network VSC driver passes the event > > > RNDIS_STATUS_NETWORK_CHANGE to the udev daemon? > > > > > > In this way, every distro only needs to add a udev rule, which should > > > be simple. > > > > No, don't do that, again, act like any other network device, drop the > > link and bring it up when it comes back. > > > > greg k-h > > Hi Greg, > Thanks for the comment! > > Do you mean tearing down the net device and re-creating it (by > register_netdev() and unregister_netdev)? No, don't you have link-detect for your network device? Toggle that, I thought patches to do this were posted a while ago... But if you really want to tear the whole network device down and then back up again, sure, that would also work. good luck, greg k-h