On Tue, Nov 01, 2022 at 08:40:06PM -0700, Jakub Kicinski wrote: > On Wed, 2 Nov 2022 01:48:09 +0100 Andrew Lunn wrote: > > Changing the interface name while running is probably not an > > issue. There are a few drivers which report the name to the firmware, > > presumably for logging, and phoning home, but it should not otherwise > > affect the hardware. > > Agreed. BTW I wonder if we really want to introduce a netconsole > specific uAPI for this or go ahead with something more general. Netconsole is a bit special because it brings an interface up very early. E.g. in our case without the netconsole the renaming is happening before the interface is brought up. I wonder if the netconsole-specific flag should allow renaming only once. > A sysctl for global "allow UP rename"? This will work for us, but I've no idea what it will break for other users and how to check it without actually trying to break :) And likely we won't learn about it for quite some time, asssuming they don't run net-next. > > We added the live renaming for failover a while back and there were > no reports of user space breaking as far as I know. So perhaps nobody > actually cares and we should allow renaming all interfaces while UP? > For backwards compat we can add a sysctl as mentioned or a rtnetlink > "I know what I'm doing" flag? > > Maybe print an info message into the logs for a few releases to aid > debug? > > IOW either there is a reason we don't allow rename while up, and > netconsole being bound to an interface is immaterial. Or there is > no reason and we should allow all. My understanding is that it's not an issue for the kernel, but might be an issue for some userspace apps which do not expect it. If you prefer to go with the 'global sysctl' approach, how the path forward should look like? Thanks!
