On Wed, 09 Aug 2017 11:03:05 +0200 Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> wrote: > Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx> writes: > > > The following would allow udev a chance at the device. > > > > This would of course work but the approach is a bit hackish and can > still fail on a loaded system. Raising the pause interval would be an > option, but again, probably not the best one. > > Let me try to send an RFC removing the check it dev_change_name() and if > it turns out that it can't be removed we can go back to your patch. But > in case it can we can leave without it. > > Thanks, I don't want to require change of semantics of core networking code for one driver. Changing name of up device has been blocked for so long that allowing it might break existing userspace apps. It might be ok in the future, but netvsc needs to work without that change. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
