From: "Michael S. Tsirkin" <mst@redhat.com>
To: si-wei liu <si-wei.liu@oracle.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
sridhar.samudrala@intel.com, davem@davemloft.net, kubakici@wp.pl,
alexander.duyck@gmail.com, jiri@resnulli.us,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, liran.alon@oracle.com,
boris.ostrovsky@oracle.com, vijay.balakrishna@oracle.com
Subject: Re: [PATCH net v3] failover: allow name change on IFF_UP slave interfaces
Date: Wed, 27 Mar 2019 18:16:23 -0400 [thread overview]
Message-ID: <20190327181433-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <f90d9dfa-f2f1-ff04-f3fe-88fa0deffdf7@oracle.com>
On Wed, Mar 27, 2019 at 01:10:10PM -0700, si-wei liu wrote:
> Another less safer option is that we just notify userspace anyway without
> sending down/up event around, as I don't see *any real application* cares
> about the link state or whatsoever when it attempts to detect rename.
How do you write a race ree handler then? ATM just detecting link up is
sufficient and covers 100% of cases. Seems like a good idea to keep it
that way.
--
MST
next prev parent reply other threads:[~2019-03-27 22:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 23:48 [PATCH net v3] failover: allow name change on IFF_UP slave interfaces Si-Wei Liu
2019-03-27 2:13 ` Stephen Hemminger
2019-03-27 2:13 ` Stephen Hemminger
2019-03-27 13:25 ` Michael S. Tsirkin
2019-03-27 20:10 ` si-wei liu
2019-03-27 22:16 ` Michael S. Tsirkin
2019-03-27 22:16 ` Michael S. Tsirkin [this message]
2019-03-27 22:31 ` si-wei liu
2019-03-27 22:48 ` si-wei liu
2019-03-27 13:25 ` Michael S. Tsirkin
2019-03-27 11:11 ` Jiri Pirko
2019-03-27 11:11 ` Jiri Pirko
2019-03-27 23:44 ` si-wei liu
2019-03-28 17:14 ` Stephen Hemminger
2019-03-28 17:14 ` Stephen Hemminger
2019-03-28 20:15 ` si-wei liu
2019-03-28 19:49 ` kbuild test robot
2019-03-28 19:49 ` kbuild test robot
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=20190327181433-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=kubakici@wp.pl \
--cc=liran.alon@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=si-wei.liu@oracle.com \
--cc=sridhar.samudrala@intel.com \
--cc=stephen@networkplumber.org \
--cc=vijay.balakrishna@oracle.com \
--cc=virtualization@lists.linux-foundation.org \
/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.