On 8/20/25 19:41, Calvin Owens wrote:
On Wednesday 08/20 at 08:31 -0700, Calvin Owens wrote:
On Wednesday 08/20 at 08:42 +0200, Michal Schmidt wrote:
On Wed, Aug 20, 2025 at 6:30 AM Calvin Owens <[email protected]> wrote:
The same naming regression which was reported in ixgbe and fixed in
commit e67a0bc3ed4f ("ixgbe: prevent from unwanted interface name
changes") still exists in i40e.
Fix i40e by setting the same flag, added in commit c5ec7f49b480
("devlink: let driver opt out of automatic phys_port_name generation").
Fixes: 9e479d64dc58 ("i40e: Add initial devlink support")
But this one's almost two years old. By now, there may be more users
relying on the new name than on the old one.
Michal
Well, I was relying on the new ixgbe names, and I had to revert them
all in a bunch of configs yesterday after e67a0bc3ed4f :)
we have fixed (changed to old naming scheme) ixgbe right after the
kernel was used by real users (modulo usual delay needed to invent
a good solution)
And, even if it is e67a0bc3ed4f that introduced it, v6.7 was the first
release with it. I strongly suspect most servers with i40e NICs running
in the wild are running older kernels than that, and have not yet
encountered the naming regression. But you probably have much better
data about that than I do :)
RedHat patches their kernels with current code of the drivers that their
customers use (including i40e and ixgbe)
One could expect that changes made today to those will reach RHEL 10.3,
even if it would be named "kernel 6.12".
(*) the changes will likely be also in 10.2, but I don't want to make
any promises from Intel or Redhat here
