[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170808.211150.2070475124549651350.davem@davemloft.net>
Date: Tue, 08 Aug 2017 21:11:50 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: otubo@...hat.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
devel@...uxdriverproject.org, sthemmin@...rosoft.com,
haiyangz@...rosoft.com, kys@...rosoft.com
Subject: Re: [PATCH] hv_set_ifconfig.sh double check before setting ip
From: Eduardo Otubo <otubo@...hat.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@...hat.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.
Powered by blists - more mailing lists