From: Eduardo Otubo <otubo@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, sthemmin@microsoft.com,
haiyangz@microsoft.com, kys@microsoft.com
Subject: Re: [PATCH] hv_set_ifconfig.sh double check before setting ip
Date: Wed, 9 Aug 2017 11:02:12 +0200 [thread overview]
Message-ID: <494db0c8-8c31-f2ce-17fc-7b96b74f0b28@redhat.com> (raw)
In-Reply-To: <20170808.211150.2070475124549651350.davem@davemloft.net>
On 08/09/2017 06:11 AM, David Miller wrote:
> From: Eduardo Otubo <otubo@redhat.com>
> Date: Tue, 8 Aug 2017 15:53:45 +0200
>
>> This patch fixes the behavior of the hv_set_ifconfig script when setting
>> the interface ip. Sometimes the interface has already been configured by
>> network daemon, in this case hv_set_ifconfig causes "RTNETLINK: file
>> exists error"; in order to avoid this error this patch makes sure double
>> checks the interface before trying anything.
>>
>> Signed-off-by: Eduardo Otubo <otubo@redhat.com>
>
> And if the daemon sets the address after you test it but before
> you try to set it in the script, what happens?
>
> This is why I hate changes like this. They don't remove the problem,
> they make it smaller. And smaller in a bad way. Smaller makes the
> problem even more harder to diagnose when it happens.
>
> There is implicitly no synchonization between network configuration
> daemons and things people run by hand like this script.
>
> So, caveat emptor.
>
> I'm not applying this, sorry.
>
This is just part of the resolution, actually. For RHEL I also configure
hyperv-daemons' systemd config file to be run only after network service
is up.
So perhaps my solution should be distro-agnostic and only involve this
script as part of it? In this case I'll elaborate a little more then.
Thanks for the comment.
next prev parent reply other threads:[~2017-08-09 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 13:53 Eduardo Otubo
2017-08-09 4:11 ` David Miller
2017-08-09 9:02 ` Eduardo Otubo [this message]
2017-08-10 7:40 ` Eduardo Otubo
2017-08-10 16:12 ` David Miller
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=494db0c8-8c31-f2ce-17fc-7b96b74f0b28@redhat.com \
--to=otubo@redhat.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@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
all inboxes | Powered by JetHome®