[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190405175429-mutt-send-email-mst@kernel.org>
Date: Fri, 5 Apr 2019 18:01:43 -0400
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Si-Wei Liu <si-wei.liu@...cle.com>, sridhar.samudrala@...el.com,
davem@...emloft.net, kubakici@...pl, alexander.duyck@...il.com,
jiri@...nulli.us, netdev@...r.kernel.org,
virtualization@...ts.linux-foundation.org, liran.alon@...cle.com,
boris.ostrovsky@...cle.com, vijay.balakrishna@...cle.com
Subject: Re: [PATCH net v6] failover: allow name change on IFF_UP slave
interfaces
On Fri, Apr 05, 2019 at 02:47:01PM -0700, Stephen Hemminger wrote:
> On Wed, 3 Apr 2019 00:52:47 -0400
> Si-Wei Liu <si-wei.liu@...cle.com> wrote:
>
> >
> > + if (unlikely(dev->flags & IFF_UP)) {
> > + struct netdev_notifier_change_info change_info = {
> > + .info.dev = dev,
> > + };
> > +
> > + call_netdevice_notifiers_info(NETDEV_CHANGE,
> > + &change_info.info);
> > + }
>
> This notifier is not really necessary, there already is a CHANGENAME
> that gets sent.
> NETDEV_CHANGE is used in other cases to mean that the state (flags)
> have changed.
The point is some existing scripts might not expect name
change to happen without a status change afterwards (since it was
impossible for so long). So this reports a change
to make sure scripts do not miss it.
Powered by blists - more mailing lists