All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Haiyang Zhang <haiyangz@microsoft.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: David Miller <davem@davemloft.net>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"driverdev-devel@linuxdriverproject.org" 
	<driverdev-devel@linuxdriverproject.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] hyperv: Add handler for RNDIS_STATUS_NETWORK_CHANGE event
Date: Fri, 30 Oct 2015 23:10:55 +0100	[thread overview]
Message-ID: <5633EAEF.5030600@nod.at> (raw)
In-Reply-To: <BN1PR0301MB07707C038A4411BD4DF24DE3CA2F0@BN1PR0301MB0770.namprd03.prod.outlook.com>

Am 30.10.2015 um 23:03 schrieb Haiyang Zhang:
> 
> 
>> -----Original Message-----
>> From: Vitaly Kuznetsov [mailto:vkuznets@redhat.com]
>> Sent: Friday, October 30, 2015 6:56 AM
>> To: Haiyang Zhang <haiyangz@microsoft.com>
>> Cc: Richard Weinberger <richard.weinberger@gmail.com>; David Miller
>> <davem@davemloft.net>; olaf@aepfle.de; jasowang@redhat.com; driverdev-
>> devel@linuxdriverproject.org; LKML <linux-kernel@vger.kernel.org>;
>> netdev@vger.kernel.org
>> Subject: Re: [PATCH net-next] hyperv: Add handler for
>> RNDIS_STATUS_NETWORK_CHANGE event
>>
>> Haiyang Zhang <haiyangz@microsoft.com> writes:
>>
>>>> -----Original Message-----
>>>> From: Richard Weinberger [mailto:richard.weinberger@gmail.com]
>>>> Sent: Tuesday, October 27, 2015 6:36 PM
>>>> To: David Miller <davem@davemloft.net>
>>>> Cc: Haiyang Zhang <haiyangz@microsoft.com>; olaf@aepfle.de; Greg
>> Kroah-
>>>> Hartman <greg@kroah.com>; netdev@vger.kernel.org; jasowang@redhat.com;
>>>> driverdev-devel@linuxdriverproject.org; LKML <linux-
>>>> kernel@vger.kernel.org>
>>>> Subject: Re: [PATCH net-next] hyperv: Add handler for
>>>> RNDIS_STATUS_NETWORK_CHANGE event
>>>>
>>>> On Mon, Jun 23, 2014 at 10:10 PM, David Miller <davem@davemloft.net>
>>>> wrote:
>>>>> From: Haiyang Zhang <haiyangz@microsoft.com>
>>>>> Date: Mon, 23 Jun 2014 16:09:59 +0000
>>>>>
>>>>>> So, what's the equivalent or similar command to "network restart"
>> on
>>>> SLES12? Could
>>>>>> you update the command line for the usermodehelper when porting
>> this
>>>> patch to SLES
>>>>>> 12?
>>>>>
>>>>> No, you are not going to keep the usermodehelper invocation in your
>>>> driver
>>>>> please remove it.  It is absolutely inappropriate, and I strictly
>> do
>>>> not want
>>>>> to keep it in there because other people will copy it and then
>> we'll
>>>> have a
>>>>> real mess on our hands.
>>>>
>>>> Sorry for digging up this old thread.
>>>> While talking with some guys about usermodehelper abuses I came
>> across
>>>> this gem.
>>>> Mainline still contains that "/etc/init.d/network restart" code.
>>>> Haiyang, care to cleanup?
>>>
>>> Hi Richard and others,
>>>
>>> Thanks for the reminder. I will clean up the usermode helper.
>>>
>>> Do you have suggestions of trigger DHCP refresh from kernel mode? Any
>>> sample code in the existing kernel code?
>>>
>>
>> I think it's wrong to call dhcp refresh from kernel. What happens when
>> we reconnect normal hardware adapter to another network? Link goes down
>> and then up and userspace is supposed to react accordingly. I think we
>> should emulate something similar for RNDIS_STATUS_NETWORK_CHANGE.
> 
> When link is down physically for a few seconds, the DHCP will automatically 
> refresh. I will add code to emulate this. There were some discussions around 
> this and other possibilities previously... I agree emulating what happens 
> with physically plug/unplug a cable is a reasonable way to trigger the DHCP 
> refresh.

Can't you propagate the event to userspace and let it take an appropriate
action?

Thanks,
//richard

  reply	other threads:[~2015-10-30 22:11 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20  1:34 [PATCH net-next] hyperv: Add handler for RNDIS_STATUS_NETWORK_CHANGE event Haiyang Zhang
2014-06-20  1:34 ` Haiyang Zhang
2014-06-20  4:21 ` David Miller
2014-06-20  4:21   ` David Miller
2014-06-20  4:57 ` Olaf Hering
2014-06-20  5:12   ` Greg KH
2014-06-20  5:12     ` Greg KH
2014-06-20 16:09     ` Haiyang Zhang
2014-06-23  8:02       ` Olaf Hering
2014-06-23 12:47         ` Haiyang Zhang
2014-06-23 12:47           ` Haiyang Zhang
2014-06-23 13:17           ` Olaf Hering
2014-06-23 13:17             ` Olaf Hering
2014-06-23 16:09             ` Haiyang Zhang
2014-06-23 16:09               ` Haiyang Zhang
2014-06-23 16:27               ` Olaf Hering
2014-06-23 18:21                 ` Haiyang Zhang
2014-06-23 18:21                   ` Haiyang Zhang
2014-06-26  8:45                   ` Olaf Hering
2014-06-26  8:45                     ` Olaf Hering
2014-06-26 14:55                     ` Haiyang Zhang
2014-06-26 14:55                       ` Haiyang Zhang
2014-06-23 16:29               ` Greg KH
2014-06-23 18:23                 ` Haiyang Zhang
2014-06-23 20:11                 ` David Miller
2014-06-23 20:11                   ` David Miller
2014-06-23 20:10               ` David Miller
2014-06-23 20:10                 ` David Miller
2014-06-23 20:17                 ` Haiyang Zhang
2015-10-27 22:36                 ` Richard Weinberger
2015-10-27 22:36                   ` Richard Weinberger
2015-10-28 17:59                   ` Haiyang Zhang
2015-10-28 17:59                     ` Haiyang Zhang
2015-10-29 19:09                   ` Haiyang Zhang
2015-10-29 19:09                     ` Haiyang Zhang
2015-10-30 10:56                     ` Vitaly Kuznetsov
2015-10-30 22:03                       ` Haiyang Zhang
2015-10-30 22:10                         ` Richard Weinberger [this message]
2014-06-23 20:06             ` David Miller
2014-06-23 20:06               ` David Miller
2014-06-20  8:41 ` Dan Carpenter
2014-06-20  8:41   ` Dan Carpenter
2014-06-20 15:48   ` Haiyang Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5633EAEF.5030600@nod.at \
    --to=richard@nod.at \
    --cc=davem@davemloft.net \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=vkuznets@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.