From: Dan Williams <dcbw@redhat.com>
To: Lennart Poettering <mzxreary@0pointer.de>
Cc: "olaf@aepfle.de" <olaf@aepfle.de>,
netdev <netdev@vger.kernel.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
LKML <linux-kernel@vger.kernel.org>, Tom Gundersen <teg@jklm.no>,
"Yue Zhang \(OSTC DEV\)" <yuezha@microsoft.com>,
Greg KH <gregkh@linuxfoundation.org>,
Thomas Shao <huishao@microsoft.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] Hyperv: Trigger DHCP renew after host hibernation
Date: Mon, 21 Jul 2014 12:17:36 -0500 [thread overview]
Message-ID: <1405963056.20886.9.camel@dcbw.local> (raw)
In-Reply-To: <20140721131154.GA23385@tango.0pointer.de>
On Mon, 2014-07-21 at 15:11 +0200, Lennart Poettering wrote:
> On Mon, 21.07.14 10:21, Yue Zhang (OSTC DEV) (yuezha@microsoft.com) wrote:
>
> > Some network monitoring daemon, like ifplugd has a deferring mechanism.
> > When it detects carriers is offline, it doesn't trigger DHCP renew immediately.
> > Instead it will wait for another 5 seconds to check whether carrier is back to
> > online status. In that case, it will avoid renew DHCP lease.
>
> ifplugd doesn't renew DHCP leases anyway, one of the scripts it invokes
> does.
>
> ifplugd is obsolete software. I wrote it more than 10 years ago, and
> haven't really updated it since. it's sounds seriously wrong to add
> multi-second waits to the kernel just to make this crappy, obsolete
> software work.
>
> Please fix this properly, and work with the PM guys, so that we get a
> sane userspace how the kernel can notify userspace about
> suspends/hibernations triggered from the outside, so that userspace
> daemons can subscribe to that and then refresh the DHCP leases on their
> own.
Yeah, like I've said before, there have been other cases where a "hey,
my L3 address might be wrong now, so please confirm it" message would be
useful. Carrier on/off doesn't necessarily mean that, but even if it
did, the off interval is a really bad mechanism for that too. So I'd
really like some kind of event for this that's distinct from carrier
that userspace could use.
Dan
next prev parent reply other threads:[~2014-07-21 17:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 10:55 [PATCH] Hyperv: Trigger DHCP renew after host hibernation Yue Zhang
2014-07-18 10:13 ` Varka Bhadram
2014-07-21 2:45 ` Yue Zhang (OSTC DEV)
2014-07-18 13:40 ` Richard Weinberger
2014-07-21 2:44 ` Yue Zhang (OSTC DEV)
2014-07-21 6:55 ` Richard Weinberger
2014-07-21 8:05 ` Yue Zhang (OSTC DEV)
2014-07-21 8:17 ` Richard Weinberger
2014-07-21 8:44 ` Yue Zhang (OSTC DEV)
2014-07-21 9:01 ` Richard Weinberger
2014-07-21 9:18 ` Olaf Hering
2014-07-21 21:32 ` David Miller
2014-08-07 22:37 ` Richard Weinberger
2014-08-08 3:13 ` Dexuan Cui
2014-08-08 3:32 ` Greg KH
2014-08-08 8:11 ` Dexuan Cui
2014-08-08 13:45 ` Greg KH
2014-08-08 16:28 ` Stephen Hemminger
2014-08-11 3:23 ` Dexuan Cui
2014-08-11 3:51 ` Florian Fainelli
2014-08-11 4:22 ` Bill Fink
2014-08-12 7:51 ` Dexuan Cui
2014-08-12 7:48 ` Dexuan Cui
2014-08-11 10:45 ` Tom Gundersen
2014-08-12 8:29 ` Dexuan Cui
2014-08-13 13:15 ` Tom Gundersen
2014-08-13 13:34 ` Dan Williams
2014-08-14 5:19 ` Dexuan Cui
2014-08-11 3:29 ` Dexuan Cui
2014-07-21 9:42 ` Tom Gundersen
2014-07-21 10:21 ` Yue Zhang (OSTC DEV)
2014-07-21 13:11 ` Lennart Poettering
2014-07-21 17:17 ` Dan Williams [this message]
2014-07-21 14:06 ` Tom Gundersen
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=1405963056.20886.9.camel@dcbw.local \
--to=dcbw@redhat.com \
--cc=davem@davemloft.net \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=huishao@microsoft.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mzxreary@0pointer.de \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=teg@jklm.no \
--cc=yuezha@microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).