> On 21 Mar 2019, at 16:04, Michael S. Tsirkin wrote:
>
> On Wed, Mar 06, 2019 at 10:08:32PM -0500, Si-Wei Liu wrote:
>> When a netdev appears through hot plug then gets enslaved by a failover
>> master that is already up and running, the slave will be opened
>> right away after getting enslave
On Thu, Mar 21, 2019 at 04:20:40PM +0200, Liran Alon wrote:
>
>
> > On 21 Mar 2019, at 16:04, Michael S. Tsirkin wrote:
> >
> > On Wed, Mar 06, 2019 at 10:08:32PM -0500, Si-Wei Liu wrote:
> >> When a netdev appears through hot plug then gets enslaved by a failover
> >> master that is already up
On Wed, Mar 06, 2019 at 10:08:32PM -0500, Si-Wei Liu wrote:
> When a netdev appears through hot plug then gets enslaved by a failover
> master that is already up and running, the slave will be opened
> right away after getting enslaved. Today there's a race that userspace
> (udev) may fail to renam
On 3/19/2019 10:20 PM, si-wei liu wrote:
Hi Sridhar,
Are you fine with leaving the IFF_SLAVE_RENAME_OK flag as is, and thus
can provide your Ack-by or Reviewed-by? I can change the code if you
feel strong.
My preference would be not to introduce a new flag unless there is any
usecase wher
On 3/6/2019 7:08 PM, Si-Wei Liu wrote:
When a netdev appears through hot plug then gets enslaved by a failover
master that is already up and running, the slave will be opened
right away after getting enslaved. Today there's a race that userspace
(udev) may fail to rename the slave if the kernel
