linux-kernel - Re: Is it possible to undo the ixgbe device name change?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3531595.1745571515@warthog.procyon.org.uk>
Date: Fri, 25 Apr 2025 09:58:35 +0100
From: David Howells <dhowells@...hat.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: dhowells@...hat.com, Jedrzej Jagielski <jedrzej.jagielski@...el.com>,
    Przemek Kitszel <przemyslaw.kitszel@...el.com>,
    Tony Nguyen <anthony.l.nguyen@...el.com>,
    Paulo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
    linux-kernel@...r.kernel.org
Subject: Re: Is it possible to undo the ixgbe device name change?

Andrew Lunn <andrew@...n.ch> wrote:

> Are you sure this patch is directly responsible? Looking at the patch

I bisected it to that commit.  Userspace didn't change.

> Notice the context, not the change. The interface is being called
> eth%d, which is normal. The kernel will replace the %d with a unique
> number. So the kernel will call it eth42 or something. You should see
> this in dmesg.

Something like this?

... systemd-udevd[2215]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
... kernel: ixgbe 0000:01:00.0 enp1s0: renamed from eth0

or:

... systemd-udevd[2568]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
... kernel: ixgbe 0000:01:00.0 enp1s0np0: renamed from eth0

I presume the kernel message saying that the renaming happened is triggered by
systemd-udevd?

David