[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210115195407.2flujwhhm24y6tty@skbuf>
Date: Fri, 15 Jan 2021 21:54:07 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, alexandre.belloni@...tlin.com,
andrew@...n.ch, f.fainelli@...il.com, vivien.didelot@...il.com,
alexandru.marginean@....com, claudiu.manoil@....com,
xiaoliang.yang_1@....com, hongbo.wang@....com, jiri@...nulli.us,
idosch@...sch.org, UNGLinuxDriver@...rochip.com
Subject: Re: Renaming interfaces that are up (Was "Re: [PATCH v3 net-next
08/10] net: mscc: ocelot: register devlink") ports
On Fri, Jan 15, 2021 at 07:11:42PM +0200, Vladimir Oltean wrote:
> By the way I removed the if condition and added nothing in its place,
> just to see what would happen. I see a lot of these messages, I did not
> investigate where they are coming from and why they are emitted. They go
> away when I rename the interface back to swp0.
Looks like it's again related to dhcpcd. If I rename the interface while
it's down, the link-local IPv6 addresses don't get endlessly deleted as
they do if I rename it while it's up. Also, if I live-rename the interface
while dhcpcd isn't up, that behavior disappears too.
Still not sure why it happens.
Powered by blists - more mailing lists